feat: add explicit page.path#749
Draft
stefanprobst wants to merge 4 commits into
Draft
Conversation
This was referenced Jul 20, 2026
stefanprobst
added a commit
that referenced
this pull request
Jul 20, 2026
include slugs in `person.position` api responses, so the website can create links to the related organisational unit. e.g. in case of a "working group chair" position, the api now returns name, type, and slug of the working group. open question: should we - in addition to name/type/slug - also resolve an actual pathname, or should we delegate the responsibility to the api consumer. this is related to #749
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this adds a
page.pathcolumn, which allows setting an explicit pathname for pages.page.slugstill exists, but only as internal indentifier.on its own this does nothing - it requires the frontend to render pages via dynamic route segment, and fetch page content via
/api/pages/by/path?page=%2Fget-involved%2Fjoin-dariah.related:
person.positionincludes entity type/slug, and also delegates resolving this to pathnames to the api consumer (see feat: include slugs in person.position api responses #753) - even though we already know the mapping server-side because we use it when populating the typesense index