Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

ethomson
Copy link
Member

A handful of improvements to the SHA256 support - especially future-proofing the options structures.

As users begin to specify the object ID types, provide an internal
mechanism to determine whether the type is valid / supported or not.
Instead of simply taking the oid type, future-proof our index opening
and creation functionality by taking an options structure.
Object ID type should be an option within the options structure; move it
there.
The `wrap_odb` function doesn't need to know the OID types in the object
database; the object database already knows the type.
Future-proof the SHA256-ification of `git_repository_new` by taking an
options structure instead of an oid type.
Instead of making the commit and dump functions take individual options
structures; provide the options structure to the writer creator. This
allows us to add additional information (like OID type) during
generation.
Provide an options structure to commit graph opening. This allows us to
specify information (like OID type) during opening.
Provide an options structure to MIDX writing. This allows us to
specify information (like OID type) during writer creation.
@ethomson ethomson merged commit 4dcdb64 into main Dec 18, 2024
38 checks passed
@ethomson ethomson deleted the ethomson/sha256 branch December 18, 2024 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant