Skip to content

feat(parser): support per-method parsers#164

Open
rmlearney-digicatapult wants to merge 8 commits into
decentralized-identity:masterfrom
rmlearney-digicatapult:feat/per-method-parsers
Open

feat(parser): support per-method parsers#164
rmlearney-digicatapult wants to merge 8 commits into
decentralized-identity:masterfrom
rmlearney-digicatapult:feat/per-method-parsers

Conversation

@rmlearney-digicatapult

@rmlearney-digicatapult rmlearney-digicatapult commented Jul 17, 2026

Copy link
Copy Markdown

NB Built on #163, will rebase if merged

DID Core v1.0 enables specific DID methods to apply stricter syntax requirements atop the base requirements of DID Core v1.0

Enable custom per-method parsers to be wrapped in getResolver() so that each method can control their own stricter syntactic parsing atop the DID Core v1.0 parser

Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
Signed-off-by: rmlearney-digicatapult <robert.learney@digicatapult.org.uk>
@rmlearney-digicatapult

Copy link
Copy Markdown
Author

I did have one thought when creating this feature - should it follow after the main DID Core parser, or replace it entirely assuming that implementers will already consume/use the main DID Core parser in their internal flows?

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.

1 participant