8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
e41cf49
1a3d465
6d19549
36fa8b3
0a99143
b2c7d32
9ed9c57
aa32896
99251c3
bebf674
5955f17
14d50e1
ff8869a
ada2471
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
quotes around "json_manifest_path"?
Sorry, something went wrong.
Just asking: would manifest_path be a more future-proof name than json_manifest_path ? Or is this too much future thinking? Can we expect to support other formats different than JSON?
manifest_path
json_manifest_path
Same for JsonManifestVersionStrategy -> ManifestVersionStrategy ?
JsonManifestVersionStrategy
ManifestVersionStrategy
It's a good thought. I don't know! It's a fairly easy thing to deprecate and change in the future anyways, and I can't see any other format in the near future. So let's go with what we like best right now. I changed to json_manifest_path because I thought it might be more clear what this manifest thing should be.
lgtm as json*