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
  • #648

Closed
Open
Opened Apr 10, 2024 by Przemyslaw Kaminski@cgenie
  • Report abuse
  • New issue
Report abuse New issue

Fix breadcrumbs

Currently we just get the hash from browser URL and try to parse node id as the last element:

https://gitlab.iscpif.fr/gargantext/purescript-gargantext/blob/dev/src/Gargantext/Components/Forest/Breadcrumb.purs#L73

But we could have done this:

{ route } <- Store.use
route' <- T.useLive T.unequal route

And now the route' variable is of type Gargantext.Routes -> AppRoute and contains all info about all the ids and sessions involved in that route, already parsed. This is more reliable than parsing the last element of the path - for things like annuaire details etc the last element is from the contexts table, not nodes.

The get breadcrumb branch GraphQL call could use the route' info to give more precise breadcrumb path. Sometimes (e.g. for document it just returns 'Home' because the last element is in contexts). See also #645 (closed)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/purescript-gargantext#648