update the file at the configured manifest file path if it exists #34
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 is a fix for a small bit of unexpected behavior when using
Papers::ManifestUpdater.new.update!to automatically update the manifest during test runs.Currently, if you configure a custom manifest file using
calling
Papers::ManifestUpdater.new.update!does not update that configured manifest file. Instead, it tries to updateconfig/papers_manifest.yml.This is easy enough to work around by passing the path like so:
But that's kind of a bummer. It would be nice if the updater used the configured manifest file if one exists - I thought so, anyway, and I hope you agree! 😄