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 175
    • Issues 175
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • 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
  • Issues
  • #63

Closed
Open
Opened Jun 24, 2021 by delanoe@anoe
  • Report abuse
  • New issue
Report abuse New issue

[Code Review / Quick Optimization] Servant API current use

  • This issue is a kind of door to enter in our backend codebase
  • Currently the maximum number of routes is limited: I remember adding 2 or 3 routes that caused some error compilation, I had to comment/remove some of them to be able to add a new one. I guess a split would fix the issue and decrease the time of compilation too. Next issues related with the API will deal with new routes, hence this fix will be useful later.
  • Code Review: Do you see how we could improve our codebase for our Servant use currently ? Any advice would be appreciated to help all the team to improve our skills (mine at least :)
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#63