Update error type returned when Roll.LatestVersionRemote
finds no version schema
#918
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.
Ensure that the error returned by
Roll.LatestVersionRemote
when there are no version schema in the target database makes it clear that there are no version schema rather than no migrations.When using
Roll.WithVersionSchema(false)
it's easy to have a situation where there are migrations applied but no version schema; in that caseRoll.LatestVersionRemote
should return an appropriate error rather than one that says no migrations have been applied.