The DidUrl parser uses URL crate to assist parsing but it's problematic as specified here. uri crate doesn't work for our case as well.
Describe the solution to the problem
So we will need to write our own parser grammar in order to properly parse a did url with optional path, query and fragment like this:
"did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a/path?query=q#fragment"
Describe the uses cases for the feature
We may need to accommodate other did format, but for now the feature would be more than enough.
Is your feature request related to a problem?
The
DidUrlparser uses URL crate to assist parsing but it's problematic as specified here. uri crate doesn't work for our case as well.Describe the solution to the problem
So we will need to write our own parser grammar in order to properly parse a did url with optional path, query and fragment like this: "did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a/path?query=q#fragment"
Describe the uses cases for the feature
We may need to accommodate other did format, but for now the feature would be more than enough.
Additional details
lyn might be a good reference.