Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could there be a way to analyse the input files without a compilation pass first? #27

Closed
7sharp9 opened this issue May 13, 2020 · 2 comments
Labels
help wanted Extra attention is needed wontfix This will not be worked on

Comments

@7sharp9
Copy link
Collaborator

7sharp9 commented May 13, 2020

Either PortaCode, or run on nuget restore are potentials.

Also we could type check the generated code as a debugging aid, not sure this is needed as pre-build step generates the code for the IDE to show errors.

@Krzysztof-Cieslak
Copy link
Contributor

So I think there are 2 levels here:

  • UsePortaCode or some crazy analyzer using FSharp.Analyzers.SDK to provide real-time errors from the analyzers by executing plugin in memory and typechecking output (difficult to do)
  • Add possibility to output errors/warnings from the plugin - and report them as normal MsBuild warnings/errors. This is easier to do but won't be "real-time"

@7sharp9 7sharp9 added the help wanted Extra attention is needed label Apr 27, 2021
@7sharp9 7sharp9 added the wontfix This will not be worked on label Oct 6, 2021
@7sharp9
Copy link
Collaborator Author

7sharp9 commented Oct 6, 2021

Probably just leave this, if someone wants to check generated code they can alway add it themselves.

@7sharp9 7sharp9 closed this as completed Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants