Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 154
    • Issues 154
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Merge Requests
  • !295

Merged
Opened Jun 10, 2024 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
Report abuse

Integrate servant-routes

Fixes #350 (closed).

This MR integrate servant-routes into Gargantext, with a new CLI option routes that can be called this way:

cabal v2-run -- gargantext-cli routes list

This will list all the available routes in the system:

GET /swagger.json
GET /swagger-ui
GET /swagger-ui/index.html
POST /api/v1.0/auth
POST /api/v1.0/forgot-password
GET /api/v1.0/forgot-password?uuid=<Maybe Text>
POST /api/v1.0/async/forgot-password/nobody
POST /api/v1.0/async/forgot-password
POST /api/v1.0/async/forgot-password/<ID 'Unsafe "job">/kill?limit=<Maybe Limit>&offset=<Maybe Offset>
GET /api/v1.0/async/forgot-password/<ID 'Unsafe "job">/poll?limit=<Maybe Limit>&offset=<Maybe Offset>
GET /api/v1.0/async/forgot-password/<ID 'Unsafe "job">/wait
GET /api/v1.0/version
GET /api/v1.0/user
PUT /api/v1.0/user
... the list goes on

As well as exporting the whole routes via JSON:

cabal v2-run -- gargantext-cli routes export --file routes.json

The latter is the most useful command, because it can be inserted into a golden test that ensures that future refactoring won't break our routes.

Edited Jul 08, 2024 by Alfredo Di Napoli

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch origin
git checkout -b adinapoli/issue-350 origin/adinapoli/issue-350

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/dev
git merge --no-ff adinapoli/issue-350

Step 4. Push the result of the merge to GitLab

git push origin dev

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 0
  • Commits 1
  • Pipelines 3
  • Changes 11
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
1
Labels
Ready to merge
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!295

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.