sourcecodeoer / sourcecode-front Goto Github PK

Hello,

As showcased here, the openapi-enforcer doesn't support to have [] in query parameters :

In a nutshell :

• http://127.0.0.1:57185/api/tags?state=pending&tags_ids=1&tags_ids=2&categories_ids=1&title=hero ✔️
• http://127.0.0.1:57185/api/tags?state=pending&tags_ids[]=1&tags_ids[]=2&categories_ids[]=1&title=hero ❌

In the axios docs, the default behaviour of the culpit ( paramsSerializer ) is explained :

  // `paramsSerializer` is an optional function in charge of serializing `params`
  // (e.g. https://www.npmjs.com/package/qs, http://api.jquery.com/jquery.param/)
  paramsSerializer: function (params) {
    return Qs.stringify(params, {arrayFormat: 'brackets'})
  },

So arrayFormat: 'repeat' should be used instead :

  // `paramsSerializer` is an optional function in charge of serializing `params`
  // (e.g. https://www.npmjs.com/package/qs, http://api.jquery.com/jquery.param/)
  paramsSerializer: function (params) {
    return Qs.stringify(params, {arrayFormat: 'repeat'})
  },

• Export exercises
• Soft and hard delete
• Contact creator of an exercise

Hello,

As the title said, It seems your validator is crazy about MIME verification :

I used zips from various source ( inginious , enseignement.be , etc ) : the bug comes from the front
as no call to the API were done ...

What can we write when it comes to the contract between a user and the application to use and exchange data.

In the main page of our own exercises, make the actions in the action selector (which is appearing when selecting at least one exercise) work for publishing and unpublish.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

When we add some filters in the main page and then go to a specific exercise, there is a bug when we go back to the main page. The selected filters are there, but we can add exactly the same filter every time we go to a specific exercise

To handle licenses, I suggest to use the SPDX License List.

Why ?

1. It comes from Linux Foundation, a quite acknowledged organization in Open Source communities.
2. The list of licenses is actively maintained and there is already NPM packages for that list
3. For every license, we can directly access to the license text by :

"https://spdx.org/licenses/" + spdxIdentifier + ".html"

Example : Creative Commons Attribution Non Commercial Share Alike 4.0 International

Hello,

I'm come up with few ideas to increase the UX :

• Use tooltip (infobulle in french) for too-longs tags

If a tag string length is above X (let's say 50 characters), a tooltip to display the full text (when we are hover this tag) is useful.
Currently, some tags are too long (it could occur for other reasons like a long course name)

• Use "rectangle with rounded corners" containers around tags for the ones inside "favories" and "historique" panels

Currently, we have something like that :

The | symbol may be not clear enough for some cases (like many tag , etc...) so why not reuse the same tag container and the same color used in the main search (except that here there is not cross to remove the tag like the main search)

Of course, because some tags have long, we could combine this idea with the previous one (the tooltip)

• Remove "Nb de" for url /administration/categories :

With the context, I don't believe it is useful to prepend "Nb de" (nombre de) in the columns titles as it seems easy to understand

Hello,

For documentation purposes, it it better to explain environment variables used in the app.
Currently, I saw only one in the nuxt.config.js file :

• API_SERVER ( url of the API server )

Endpoint to use : /api/bulk/create_exercises ( the application/json version)

Use database with true data to complete this section