Flexible mapping provider to parser #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chadell
force-pushed
the
flexible-mapping-provider-to-parser
branch
from
9567288
to
b65b612
Compare
chadell
changed the title
glennmatthews
previously approved these changes
Aug 6, 2021
|
@glennmatthews I'm gonna merge this as it's already approved and 3985590 only updated the Readme and Changelog |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #43
It creates a new custom field in
Providerthat can be used to define a custom Provider name in thecircuit-maintenance-parserlibrary, and when not provider, theProvider.slugwould be used, same as today.