Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
purescript-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 140
    • Issues 140
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • 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
  • purescript-gargantext
  • Issues
  • #639

Closed
Open
Opened Mar 18, 2024 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
  • New issue
Report abuse New issue

Remove `All` constructor

Following the backend MR haskell-gargantext!261 (merged) , we have now removed the All data constructor from the Lang type, and we should do the same on the frontend code, to avoid impedance mismatches.

In practice, however, I don't think the frontend is ever sending to the backend corpus search where the lang is All : from my empirical tests I have seen that by default the frontend will send EN as a language if the user didn't specify a preference or if the search API provider doesn't support searching in other languages rather than english.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
toClose?
Assign labels
  • View project labels
Reference: gargantext/purescript-gargantext#639