Skip to content

fix(acl): expose ParseOptions on dataset fetch helpers - #2971

Open
kmlyz wants to merge 1 commit into
inrupt:mainfrom
kmlyz:fix/expose-parse-options
Open

kmlyz wants to merge 1 commit into
inrupt:mainfrom
kmlyz:fix/expose-parse-options

Conversation

@kmlyz

@kmlyz kmlyz commented Nov 6, 2026

Copy link
Copy Markdown

This PR fixes #2529.

  • I've added a unit test to test for potential regressions of this bug.
  • The changelog has been updated, if applicable.
  • Commits in this PR are minimal and have descriptive commit messages.

@kmlyz
kmlyz requested a review from a team as a code owner November 6, 2026 01:29
@kmlyz
kmlyz force-pushed the fix/expose-parse-options branch from d0ab16d to fbf5cfa Compare November 6, 2026 01:37
@NSeydoux

NSeydoux commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Thanks for opening this PR, let me have a look at it soon

getSolidDatasetWithAcl, getSolidDatasetWithAcr,
getSolidDatasetWithAccessDatasets, and WebID profile helpers did not
include ParseOptions in their options parameter types, preventing
callers from supplying custom RDF parsers for non-Turtle resources.

Extend the options types on these dataset-fetching functions with
Partial<ParseOptions> and forward parser options to underlying
getSolidDataset calls.

Fixes inrupt#2529
@kmlyz
kmlyz force-pushed the fix/expose-parse-options branch from fbf5cfa to ef152eb Compare November 7, 2026 19:12

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose ParserOption on more places

2 participants