Nadeeshaan Gunasinghe
Nadeeshaan Gunasinghe
@nixel2007 I was thinking if we can provide the same behaviour as in VSCode since VSCode properly provides the diagnostic in this scenario.
@nixel2007 please refer the following,
If we are to support this behaviour, we need to introduce a fail-safe `ContextTypeResolver` which can deal with the compilation errors by falling back to a known set of error...
@neojski sorry for the late reply, since I have mistakenly missed the notification. At the moment we have converted the visualization in to react by using your logic. Some of...
@neojski we are definitely mentioning you as the owner of the core logic :) . We still did not do so since we are not in a merging state. IMO...
@neojski can you give me a brief introduction about the code base? I think you have included the browserify in the code base and would be a great help if...
@robertkowalski I followed the tutorials weeks ago to understand what browserify is and read some blog posts to get an idea about it. Thanks to you I could read the...
@neojski I figured out the thing I previously asked. Without building time to time we can run the watchify to poll on the changes. I will send a master PR...
@TiloSchreiber thanks for reporting the issue. I'll send a fix and in the meantime feel free to send a PR for fixing this issue, which will be really awesome :)
@HirumalPriyashan I agree that we need a way to open the try it editor at any time. But, consider showing this for a newly added but incomplete source as shown...