You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when attempting to compile a .NET library for WebSharper fully, if any basic type is not proxied (does not have a WebSharper/JavaScript implementation), every use of the type or any of its methods generate an error. This can be a long list with many repetitions although possibly there are only a couple missing types.
As a quick solution, these errors could be tracked and only reported at the first occurrence. This is not compromising build result but gives a much shorter list of errors to work through.
The text was updated successfully, but these errors were encountered:
Thinking about this a bit more, when the goal is not to proxy missing types but to work through the code and eliminate the type (switch to using something else), original error reporting (all locations) is better. So I am making it a compiler setting, with old behavior kept by default.
Jand42
changed the title
Do not give repeated errors on missing type/methods
Do not give repeated errors on missing type/methods optionally
Oct 23, 2019
Currently, when attempting to compile a .NET library for WebSharper fully, if any basic type is not proxied (does not have a WebSharper/JavaScript implementation), every use of the type or any of its methods generate an error. This can be a long list with many repetitions although possibly there are only a couple missing types.
As a quick solution, these errors could be tracked and only reported at the first occurrence. This is not compromising build result but gives a much shorter list of errors to work through.
The text was updated successfully, but these errors were encountered: