Skip to content

Conversation

@nick-hunter
Copy link
Contributor

This should be a fix for Issue #240. Previously a bit field followed by a nest would generate parser code in the wrong order. This PR adds additional logic to determine if the next field is a bit field or not. If the next parser is a nest, we now examine the first field in it. I'll try to add some additional test cases but just want to get this open so the review process can start. Currently all test cases pass.

@nick-hunter
Copy link
Contributor Author

Just want to follow up on this. Is there anything additional I can do for this PR?

@keichi
Copy link
Owner

keichi commented Jul 17, 2023

Sorry for the delay, this looks good. As you might have guessed, the bit parsers haven't been extensively used. Your debugging is really helpful!

@keichi keichi merged commit 45a1b6e into keichi:master Jul 17, 2023
@nick-hunter
Copy link
Contributor Author

Thanks for all of your work on this library! It's been very helpful. I saw you've been working on some other housekeeping changes. Are you planning to release a new version of the library on NPM soon?

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