Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
feature request: no curly-components
See original GitHub issueI’d love a rule to help transition from {{foo-bar}} to <foo-bar>. I don’t know if it would be possible, though, since helpers would still need to be allowed.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to say no to product feature requests - Canny Blog
Figuring out how to say “no” to a customer is never easy. It's especially hard to say no to product feature requests. Many...
Read more >How to Say No To Feature Requests - FeedBear
Wondering how to say no to a customer requesting a feature you can't build? Here are some practical tips.
Read more >How to Say 'No' To Feature Requests? - UseResponse
Saying 'no' to customers' feature requests is something that product development teams ... Learn how to say 'no' in a positive and polite...
Read more >Feature Request Template: How to Manage Suggestions at ...
Streamline and organize user feedback with this free feature request template. Available in Google Docs and Sheets (no email required).
Read more >Feature request response email templates - LiveAgent
Feature requests are messages that customers send to inquire about a feature that is not included in your product or service. Receiving feature...
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
I think the rule could have a
whitelistoption to provide a list of allowed components, this option would help to have a smoother and incremental transition.I think this has been addressed, there is now a rule for
no-curly-component-invocations.