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 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • 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
  • Grégoire Locqueville
  • purescript-gargantext
  • Repository

Switch branch/tag
  • purescript-gargantext
  • src
  • Gargantext
  • Core
  • NgramsTable
  • Functions.purs
Find file
BlameHistoryPermalink
  • Przemyslaw Kaminski's avatar
    [ngrams] ngramsValidPatch put to appropriate use · 99598e59
    Przemyslaw Kaminski authored Sep 28, 2023
    For ngrams table, we set ngramsValidPatch = mempty because the table
    is refreshed and we have issue
    gargantext/purescript-gargantext#594
    
    However, we need to keep that field, it turns out, because we have
    gargantext/purescript-gargantext#598
    
    Recently applied patches are needed for the document ngrams
    highlighting.
    
    This all would be unnecessary (or at least moved to the backend) if we
    had
    gargantext/purescript-gargantext#553
    99598e59
Functions.purs 23.4 KB
EditWeb IDE

Replace Functions.purs

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.