Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add require_full_match option #448

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

max-sixty
Copy link
Sponsor Contributor

@max-sixty max-sixty commented Mar 2, 2024

May need some refining.

Closes #351, but with an additional option, since force_update seems like a bad term for this

Is this reasonable in principle?

May need some refining. Closes mitsuhiko#351, but with an additional option, since `force_update` seems like a bad term for this
@mitsuhiko mitsuhiko merged commit 686de75 into mitsuhiko:master Mar 2, 2024
6 checks passed
@mitsuhiko
Copy link
Owner

I'm good with merging this though in practice I can only assume this is probably going to be a rare thing.

@max-sixty
Copy link
Sponsor Contributor Author

max-sixty commented Mar 3, 2024

I'm good with merging this though in practice I can only assume this is probably going to be a rare thing.

Yes very possibly!

Though I find that having old metadata can be confusing ("that input generated the output on an old version of the library?!") and so enforcing up-to-date metadata is useful.

@max-sixty max-sixty deleted the require-full-match branch March 3, 2024 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should force_update error in CI when updates are required?
2 participants