Template variables won't work
See original GitHub issueOn Variables > New
page:
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Variables not working in included templates (html/template)
You have to pass the variables to the template : {{ template "head" . }}.
Read more >Typing $ to create or list template variables does not work - Jira
Type $ and the variable name, then press Enter to add a new variable or to select an existing variable from a list...
Read more >Template Variables not working for Windows 64 bit version
The template variable feature is not working as expected. What are you expecting to see happen? : To summarize the template variables work...
Read more >Live template variables don't work in Includes and Code ...
The original issue with Live Templates not working in File templates can't be reproduced in the IDE version 2020.3, however, I can't still...
Read more >Understanding template variables - Angular
Template variables help you use data from one part of a template in another part of the template. Use template variables to perform...
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
Sure, in my case I’m using a couple of dashboard variables that I retrieve from a server API for each user, something like this: To configure the dashboard variables I go to dashboard settigns -> Variables, and then I configure the variable as a query like this:
This calls the /search endpoint with the data {“target”:“LocationID:98edea1000c1b20009d9xxxx.SensorID.*”} and in this case I return the tags available for that location.
Then when the /query endpoint is called I receive the value of those variables and I can provide the correct data to the user.
This was working with version 0.1.4. I have done a bit of research and I found this recent pull request: #55 has changed the name of the function metricFindQuery -> findMetricsQuery.
Could this be related to this issue?
For now @denisidoro you can stick with version 0.1.4, is ok there