Hi EJ! Thanks for your comment. Sure, what you're saying is similar to what we suggest in the article of putting server side variables inside a global variable. The goal of the article is to point out how to avoid making an app vulnerable through bad practices, and your example seems to be in line with that :)
Hi Nando. The standard (and only) way to show a value coming from outside is to put it into a property (data, props, vuex, ...) and then show it in the template via the mustaches, v-text or v-html.
That global variable trick is a solution to a non problem.
Your "constructor" example had been discussed and should be a thing of the past.
I'm replying here because I found your article on Hacker News last week, and thought that it can generate FUD to those learning any reactive framework.
Like your hint to limit the use of Vue...
Peace :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi EJ! Thanks for your comment. Sure, what you're saying is similar to what we suggest in the article of putting server side variables inside a global variable. The goal of the article is to point out how to avoid making an app vulnerable through bad practices, and your example seems to be in line with that :)
Hi Nando. The standard (and only) way to show a value coming from outside is to put it into a property (data, props, vuex, ...) and then show it in the template via the mustaches, v-text or v-html.
That global variable trick is a solution to a non problem.
Your "constructor" example had been discussed and should be a thing of the past.
I'm replying here because I found your article on Hacker News last week, and thought that it can generate FUD to those learning any reactive framework.
Like your hint to limit the use of Vue...
Peace :)