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

Change EncryptedRequest 'id' field to String #336

Merged

Conversation

yeastplume
Copy link
Member

(Replaces #334, with a saner commit history)

In doing some sample code for the V3 API, it became evident that the ID field in encrypted requests shouldn't be restricted to being a u64, or a string representation of a u64. It should allow all types of IDs in so long as they're strings, including UUIDs.

This changes the EncryptedRequest/Response fields to type String, and provides a custom legacy serializer to ensure anyone currently sending ids as ints won't be affected by the change.

@yeastplume
Copy link
Member Author

Tested locally, tests are consistently failing due to croaring.

@yeastplume yeastplume merged commit da064ac into mimblewimble:master Feb 18, 2020
@yeastplume yeastplume deleted the encrypted_request_as_string_2 branch March 3, 2020 08:37
antiochp pushed a commit to antiochp/grin-wallet that referenced this pull request Aug 7, 2020
* change ID field in encrypted request/response to be a string of any kind

* Use JsonId Enum instead of String value
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.

None yet

1 participant