thisTag is showing an warning
See original GitHub issueThe thisTag
is proper scope when you are using custom tags. Currently, for the following code:
<cfif thisTag.executionMode eq 'start'>
</cfif>
I get VAR_HAS_PREFIX_OR_POSTFIX
Warning. Which really you shouldn’t in a custom tag.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
How can I suppress "The tag <some-tag> is unrecognized in ...
This is a new warning message in React 16. Has nothing to do with anime/react-anime and this warning can safely be ignored. It's...
Read more >Warning: [Minor] Tag 'keywords' not defined - C:/...jpg
When I run the -XMP... command you showed me, I get the "keywords not defined" warning, and when I add a keyword to...
Read more >Enable External Email Warning & Tag in Office 365 and Outlook
In this article, I will explain how you can enable the Exchange Online External Tag and create custom external email warnings in Office...
Read more >Warning on Tag Helper in UI for ASP.NET Core | Telerik Forums
I am using the following simple TagHelper: <kendo-datepicker name="DatePicker" for="Date" style='width: 280px;'> </kendo-datepicker>.
Read more >How Email Warning Tags help users protect the ... - YouTube
Learn more about the new Proofpoint Email Warning Tags with Report Suspicious: https://www.proofpoint.com/us/resourc... … Show more.
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 FreeTop 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
Top GitHub Comments
I’m not sure this is worth so much consideration given the uncertainty of determining context. What are the chances someone will name their variable
thisTag
? This is just an INFO-level rule anyway. More importantly, this is implemented as a parameter that can be configured now.Yeah, I agree - just wanted to raise the point of ambiguity in custom tag contexts. Let’s go with @ryaneberly’s fix and see if it causes any comments/concerns from anyone running into weird scenarios.