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 164
    • Issues 164
    • 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
  • Merge Requests
  • !129

Merged
Opened Feb 13, 2023 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
Report abuse

WIP: Add script to track Haskell deps, add `weeder`, remove unused `monad-logger-aeson`

Nothing too exciting for now, while I'm working my way through #180.

This MR does the following:

  • It makes the project weeder-friendly by adding a weeder.dhall config file. This is not strictly necessary and we can drop commit d40821bdc83dfe4be23132149cb835f4b54ecacb if we don't think it's useful;
  • It fixes the building of the tests by exposing Gargantext.Core.Viz.Graph.Types;
  • It adds a script for tracking Haskell deps which I have resurrected from another project of mine. It can be called as a normal shell script like ./bin/track_haskell_deps.hs and it outputs a table like the one here, which can be used to track down redundant/heavy-deps.
  • It removes monad-logger-aeson which is currently unused but it was bringing two "unique deps" to the project.

I have also started looking into reducing the number of forks, but that could take a while.

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-180-deps-audit origin/adinapoli/issue-180-deps-audit

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-180-deps-audit

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 4
  • Pipelines 1
  • Changes 6
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!129

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.