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 159
    • Issues 159
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • 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
  • #389

Closed
Open
Opened Aug 23, 2024 by Grégoire Locqueville@glocqueville
  • Report abuse
  • New issue
Report abuse New issue

Update and Improve Weeder File

The Weeder configuration file format used to be .dhall, but it has switched to .toml. The author has provided a conversion script from one to the other.

Once the transition is done to .toml, the Weeder configuration file should also be updated to include functions that should exceptionally not be treated as dead, even though they are not called from anywhere. Right now I can only think of functions in Gargantext.API.Dev, which allow for interacting with the database through GHCI, but maybe there are other ones.

In any case, there should be comments in weeder.toml explaining why exceptional functions are treated as such.

Edited Aug 23, 2024 by Grégoire Locqueville
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#389