Deprecate var, invoke, assign
See original GitHub issueWith the new $ <code>
syntax, we have a better way to add JS to a template and no longer need these tags. We do want to make them available for the v3 -> v4 migration. Should we just add a deprecation warning or split them out into a marko-v3-compat
package?
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (13 by maintainers)
Top Results From Across the Web
Why does my variable show it's deprecated? - Stack Overflow
In VS Code, find the variable name where it is showing deprecated name. Put your cursor and right click on it, then select...
Read more >Approaches to Deprecating Code in JavaScript | CSS-Tricks
In my opinion, large teams or projects relying on external APIs or libraries ought to deprecate first, then remove later (after a reasonable ......
Read more >Stop using var for declaring variables !!! - DEV Community
To achieve this, we eliminate the use of var for declaring a variable and use let & const instead for variable declaration.
Read more >Underscore.js
Underscore provides over 100 functions that support both your favorite workaday functional helpers: map, filter, invoke — as well as more specialized ...
Read more >How do I use Custom Variables? (deprecated) FAQ
Custom variables are assigned in JavaScript by calling setCustomVariable( index, name, value, scope ) to set a new custom variable to a visitor ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Let’s be honest here: We don’t get PHP simply because of
<? ?>
tags. Unless you consider Ruby on Rails and ERB to be PHP as well!I do find the
<var x=10>...</var>
feature interesting. To avoid potential confusion with JS, maybe you could rename it to something like<scoped x=10>
, for those who want that feature.I think a migration package is a good idea. If one intends to move from v3 to v4, installing a package would be the least of those efforts.
What do you mean by sub packages that export tags?