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
We should expand preloaded schemas from #302 to include both "Official" and "Verified" assuming the resulting binary is not prohibitively large and performance is not adversely affected.
The text was updated successfully, but these errors were encountered:
We discussed this before, but I'll just note it here for posterity:
In addition to the binary size, the codebase size is also a concern, so as part of this work we should consider generating schemas as part of the release. Sadly this will make builds practically unreproducible, but I think it's ok trade-off for the value added and considering this is mostly a temporary solution until #193 is resolved.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
Feb 5, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should expand preloaded schemas from #302 to include both "Official" and "Verified" assuming the resulting binary is not prohibitively large and performance is not adversely affected.
The text was updated successfully, but these errors were encountered: