Nexus Reflection as IDE process

[jasonkuhrt]

Perceived Problem

• If user forgets to run reflection then they will not get the static type feedback they expect from their Nexus project

Ideas / Proposed Solution(s)

• Create a Nexus VSCode plugin that basically runs nexus dev --reflection in the background
• Users would then run nexus dev --no-reflection
  • But we should be able to automate this with Nexus auto-detecting that the IDE variant is running
• To maintain reflection feedback the reflection process being run by the IDE should send its output to the neuxs dev process run by the user
• If the user is not running their own Nexus dev process then then the output should be visible in VSCode itself, maybe as a new Nexus pane and/or integrated into the "problems" output of VSCode
• Maybe the VSCode reflection output integration will be good enough and so there should be an option for users to not have the IDE process forward output to the user process. The presumption being that users would not like to see the same errors/warnings twice (once in IDE, once in terminal).
• If the IDE can run reflection in the backgorund, maybe we should go further and not even have the user need to run nexus dev at all. This is probably more complicated from a product point of view though and better suited as its own new issue for the future.

[jasonkuhrt]

@Weakky has already created a prototype that did this. Can you re-share your screencast video link demoing your work here?

[BiscuiTech]

Hey, just popping here because I was directed to this issue from this page. I realized this project is somewhat archived, but any chance this idea may transfer soon to nexus/schema? Thanks for your awesome work.