Skip to content

Updated CBORParser to use relative data indices #18

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

Merged
merged 5 commits into from
Oct 19, 2021
Merged

Conversation

SomeRandomiOSDev
Copy link
Owner

No description provided.

joskuijpers and others added 5 commits June 19, 2020 23:29
Data uses slices which may not start at 0. When a Data is supplied which does not start at 0, the first index previously used would throw a bad access exception.

This happened for example with a Data value returns from CBOR previously. It does not per-se start with a slice at 0.
Updated CBORParser to use relative data indices, removed nullability of CBOR.CodingKey initializers & updated CBORParser tests to test parsing sliced data
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.

2 participants