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

Scan code for save() (and other issues) before upload #214

Open
gfwilliams opened this issue Jan 24, 2020 · 1 comment
Open

Scan code for save() (and other issues) before upload #214

gfwilliams opened this issue Jan 24, 2020 · 1 comment

Comments

@gfwilliams
Copy link
Member

It seems common to put save() at the end of code in the editor. This works (but is not recommended) when you upload to RAM, but if you upload to flash it's a disaster, causing a large flash write (and reset) every time the device boots.

We should detect this (and maybe other issues) before upload and warn...

@gfwilliams
Copy link
Member Author

Should also scan for reset = and other assignments that might overwrite built-in functions.

Maybe we should just use eslint in codemirror and show the errors as they are being written?

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

No branches or pull requests

1 participant