-
Notifications
You must be signed in to change notification settings - Fork 118
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
Use proxies to avoid not defined error blocking compile #472
Comments
Currently blocked Will affect #479 |
Here is an example of the current frustration:
|
@jasonkuhrt Any workaround for this? |
@izio38 the work around for now is fix all errors before continuing. |
I'm sorry, but I can't understand what errors needs to be fix. For some reason, the compilation just doesn't pass and I'm not able to see what else is wrong. Thanks for the quick answer. |
@izio38 Try commenting out all the errors, then incrementally bring them back and debug one by one. |
I'm not sure I agree here? These are TypeScript errors. The "workaround" is just to run the server with |
@Weakky right you are |
Analogy: Unused variable as error prevents build. At dev time this is annoying because an unused variable may just be a temporary state while working towards some idea, refactor, etc. It is much better at dev time to have this feedback at the level of just a warning, that does not block the compiler from building your code.
The idea is to implement the
t.model
operation publishers andt.crud
field projectors as proxies so that when there is a sync issue or typo TS compile can still succeed. With proxies we can:please sync
etc.)We may want a prod mode where proxies aren't used.
The text was updated successfully, but these errors were encountered: