feat: rewrite the parser gathering logic #1476
Merged
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.
Instead of forcing the user to register one of the four paresers and being stuck with only those contexts, users can now add parers to a
providers
array and let theDiscoveryService
find the parsers and then use the correct one based on the context type. This allows for custom contexts like necord'sdiscord
context, to have parsers created and used for it without having to change the context or assume a certain type for it.Docs, changesets, and extra tests to come soon
related: #1451