Add way of providing external instances without an existing file #782
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 adds a new interface
InstanceProvider
which can be used to provide custom instance "parsing", but without needing an actual file to be referenced bysrc
. This makes it a lot easier to write tests for custom parsing (we don't need to deal withReferenceManager
) that don't actually care about the file insrc
, and will allow us to also provide instances without an underlying file.What has been done to verify that this works as intended?
New tests.
Why is this the best possible solution? Were any other approaches considered?
We alternatively could have made
FileInstanceParser
implementations handle convertingsrc
to an actual file path, but this would have meant changing that interface and also duplicating a bunch of code that's currently shared.How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
This just adds a new plugin interface, so there's not a lot of risk.