Support '@' symbols in resource names and vhosts #59
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 PR addresses issue #33.
Problem:
The current method of parsing a resource id in the
parseId
function uses the "@" symbol as a delimiter.This causes issues when either the name of the resource or the vhost contains "@" symbols, leading to incorrect splitting and an error to be raised.
Solution:
Implemented percent encoding for "@" symbols found in the name/vhost when combining them as a "composite resource id".
Then, during parsing, we split the resource id and then apply percent decoding to retrieve the correct values.
This approach ensures accurate parsing while being backward compatible with existing resource IDs.