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.
No template syntax in html attributes.
See original GitHub issue<i class="large shop{{ basket.error|yesno:" red," }} icon"></i> for instance is really hard to read.
Happens a LOT with href too.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
The Content Template element - HTML - MDN Web Docs
The <template> HTML element is a mechanism for holding HTML that is not to be rendered immediately when a page is loaded but...
Read more >HTML template tag
The <template> tag supports the Global Attributes in HTML. More Examples. Example. Fill the web page with one new div element for each...
Read more >Template Syntax | Vue.js
Vue uses an HTML-based template syntax that allows you to declaratively bind the rendered DOM to the underlying component instance's data. All Vue...
Read more >Template syntax
Almost all HTML syntax is valid template syntax. However, because an Angular template is part of an overall webpage, and not the entire...
Read more >Using attributes in templates | Theming Drupal
There should not be any space between the tag name and the Twig syntax. The "stable" theme included with Drupal 8 core has...
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
@willstott101 you are welcome to contribute if you want. Djaneiro is still being used by many people and it would be nice if we could solve some of those issues.
Once I feel like it’s in a reasonable position I’ll open a PR for sure (I made sure I used the same license to make that easier). Perhaps trying to make a new Package is totally pointless… to be honest I thought there was more non-syntax stuff in this Package than snippets and it made sense to have a separate pure-syntax Package. I’m not so sure now, I may cancel my packagecontrol.io request if I end up trying to merge into this repo before it’s accepted.
EDIT: I also had no idea how long it would take to develop, it’s been quicker than I imagined.