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 163
    • Issues 163
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • 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
  • #319

Closed
Open
Opened Feb 29, 2024 by Julien Moutinho@julm
  • Report abuse
  • New issue
Report abuse New issue

duckling fork

This issue is a reminder that gargantext currently uses a fork of duckling (branch adinapoli/ghc947-compat).

As of february 2024:

This branch is 6 commits ahead of facebook/duckling:main.

Related MR: !231 (merged)

Duckling doesn't work with aeson;

This fork also depends on text16-compat:

Update: I have fixed duckling by relying on a package I've developed for the occasion called text16-compat which exposes some compat shim that allows duckling to keep working even though the underlying text library is now using a ByteArray of UTF8 code points.

Edited Feb 29, 2024 by Julien Moutinho
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#319