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.
Using curly braces {} for templating content
See original GitHub issueOne of the consumers of our system uses curly braces for content replacement in strings.
Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.
I have tried a number of ways to escape the braces with no luck
Other languages and templating systems seem to use the concept of using double curly braces to handle this scenario.
It could be a way that SD could also handle it but am open to anything else that would allow the scenario to be achieved
e.g.
screenHeadingContent: {value: "Welcome's to the {{0}} screen"}
would build to
screenHeadingContent: "Welcome's to the {0} screen"
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@creatorpiyush absolutely! (sorry for the delayed response) 🐌
Can I take this issue if no one is working on it?