Simplify control flow in sample code.

[mattparlane]

eslint's default rule set includes the no-continue rule, which disallows any use of the continue keyword. This keyword is used in the project's sample code.

no-continue rule eslint's default rule set

This PR removes the continue keyword, and removes the doneReading variable from most of the sample code, and is functionally equivalent.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nlux-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 10, 2024 1:21am

[salmenus]

Thank you for this contribution @mattparlane Merging it

Feel free to apply the same change to the main code base. I'm sure you'll find some continue statements

[mattparlane]

Thanks for accepting. The thing is that I don't actually agree that the continue keyword is a problem, the only reason I thought the sample code should change is that the rule is in eslint's default config, so anyone using eslint in their project would have errors if they copied the sample code (like I did). If you're not using eslint in nlux (or you have that rule disabled), then it's not a problem, so I don't think anything else needs to change.

[salmenus]

Fair enough. We're using eslint on the main codebase, but with different config.

Thanks for fixing it for examples to match default eslint config.