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

refactor: Changed the behavior of batch-register #77

Merged
merged 3 commits into from
Aug 11, 2021

Conversation

NickolausDS
Copy link
Collaborator

Batch register now always registers a new Minid by default. A new
option, 'update_if_exists', is available to use an existing Minid
supplied in the url field if it is present, and update it instead.

This change resulted from discussion reviewing the bug report
here #75, and how this could result in undesirable behavior if
the checksums for given files were 'common' (for instance, if a
file was empty or contained content such as '1', this could return
another persons Minid).

Batch register now always registers a new minid by default. A new
option, 'update_if_exists', is available to use an existing minid
supplied in the `url` field if it is present, and update it instead
of registering a brand new minid.
minid/minid.py Outdated Show resolved Hide resolved
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.

1 participant