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.
Selected Parser not persisted upon save
See original GitHub issueTo start with, thanks so much for the excellent tool!
Reading https://github.com/fkling/astexplorer/issues/67#issuecomment-162856324, it leads me to believe that the expected behavior currently is that the selected parser should be persisted when you Save a transform. That does not seem to be working for me currently with new transforms I create on the site.
Was there a recent regression, or am I possibly just overlooking something?
I should note that, the selected parser does still show for the example that was linked in #67 (http://astexplorer.net/#/np0DfVT78g).
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 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
You rock @fkling - thank you!
Only locally though 😉 Parser settings are not stored in Parse yet. I guess we should do that at some point. Right now, the parser settings are only accessible from within each parser. I want to refactor how parser settings work soon, so that they can be passed in from the outside (e.g. an API). Then it would also be easier to save them with the code snippet.