-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Use const instead of var when outputting es6 descriptor #667
Comments
ES6 wrapper for reference: https://github.com/dcodeIO/protobuf.js/blob/master/cli/wrappers/es6.js The $root var is generated on the JS side (shared for all sorts of static code), which is then just wrapped with the wrapper referenced above. What you can do today is providing a compatible linter configuration to |
Ah, I see. What about separating the templating process out so that the assignments go to their respective sides, putting |
For reference:
As you can see there, Also, with static code there are |
I feel like I'm looking at something that resembles view logic in a web application. What would your thoughts be on pulling in a view engine as a dev dependency and doing lots of this declaratively? |
I'd rather avoid rewriting everything (again). Nonetheless, there is an |
Completely understandable. I'll try it out this evening and if there are any issues, I'll reopen :) |
I've got this in my descriptor/metadata:
Which makes my default-configured linter a little sad. Maybe it's worth switching to
const
or failing thatlet
?The text was updated successfully, but these errors were encountered: