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.
Rendering with id and default value
See original GitHub issueIn my staging environment I want to wrap my translations with a span, so the translator can hover the text to see which translation key needs to be used.
I’ve checked the defaultRender and render methods and this could do the trick, but I need access to the message id and the default message, this is not passed through.
My suggestion would be to pass it through when a Component is used in the render methods, ie:
({id,default,translation}) => translation
Any thoughts?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (5 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
I had exactly the same usecase in my mind yesterday when I was refactoring
Transcomponent. This could work as an in-context editor. You would have a expandable sidebar with a list of all messages on the page. Then we just need a local server which will communicate with sidebar and we can even edit/save messages from the website 👌I’m closing it in favor of
nextbranch and upcoming v3 release. Feel free to send a PR if you want to backport it to v2.