Skip to content

Conversation

@olomix
Copy link
Contributor

@olomix olomix commented Jul 6, 2023

No description provided.

@olomix olomix changed the base branch from main to v2 July 6, 2023 16:01
@olomix olomix requested a review from vmidyllic July 10, 2023 08:40
@olomix olomix marked this pull request as ready for review August 15, 2023 08:35
@olomix olomix merged commit b0ff7c5 into v2 Aug 15, 2023
@olomix olomix deleted the field_path_options branch August 15, 2023 08:36
vmidyllic added a commit that referenced this pull request Aug 21, 2023
… v2 (#62)

* Upgrade github.com/iden3/go-iden3-core to v2 and bump self version to v2.

* Upgrade go-iden3-core to latest version

* Modify NewPathFromDocument function to support nested fields

* Pass MerklizeOption[s] to MerklizeJSONLD

* Add merklizer options to ParseClaim method

* add Iden3StateInfo to resolvement info

* Sync with did resolver driver (#72)

* add stateContractAddress field to Vm

* Make FieldPathFromContext method for Options (#74)

* Slot serialization (#75)

* Remove ParseSlots public method. Should use ParseClaim and get slots from there.

* jsonSchemaBytes parameter is non-neded in ParseClaim, we get @serialization data from @context of the credential.

* find a credential type not only looking at crentialSubject.@type, but also looking at top level @type field

* drop credentialType parameter from ParseClaim method, it should be calculated from VerifiableCredential document

* make struct ParsedSlots private

* Rewrite GetFieldSlotIndex function to work with @serialization attribute in json-ld schema

* Upgrade go version

* Rename @serialization to iden3_serialization to prevent safe mode warning about reserved keys

* return error is MerklizedRootPosition is set for non-merklized claims

* Move DocumentLoader to loaders module* Update README

* Negative and big integers (#76)

* Handle negative and big numbers in merklizer

---------

Co-authored-by: vmidyllic <74898029+vmidyllic@users.noreply.github.com>
Co-authored-by: Ilya <officalbatya@gmail.com>
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.

3 participants