-
Notifications
You must be signed in to change notification settings - Fork 44
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
Telescope upgrade #44
Conversation
Fixed all the comments, casing, and issues from before, should be in better shape!
|
Yeah, let's include them. You find them in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing! Let's get the ICA types in here (rebase to latest main and do a git submodule init && git submodule update
then you have them). Otherwise 🏅
"Will Clark <willclarktech@users.noreply.github.com>" | ||
"Simon Warta <webmaster128@users.noreply.github.com>", | ||
"Will Clark <willclarktech@users.noreply.github.com>", | ||
"Dan Lynch <pyramation@gmail.com>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥰
* telescope-upgrade: (25 commits) context fix import as fix Misbehavior pagination field optionality optionality tslint disable RPC comments RPC interface comments toJSON Duration enum spacing enum spacing enums upgrade Duration types upgrade fromJSON eslint-disable eslintDisable run codegen update codegen settings ...
Telescope with ica
the check is giving:
I think I know how to solve this, but will make a large diff. UPDATE: I'm able to fix this, it does make a large diff. See comments below. |
btw — we can try doing this for only the google module if you want to keep the I found this error before and it's the meta typing (that I found quite unnecessary) that causes the memory issues. FYI seems that you were around when they did this stuff and may have more context:
other related issues/prs |
OK, I think that may be it! Only difference should be Exact vs DeepPartial, etc., but this method works and is much faster for the TS compiler to deal with. We can roll back the Exact/DeepPartial stuff, but then the CI can't process things because of TS compiler memory. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, let's give this a shot. I created a branch 0.5 for patching the old setup as long as we need it. This goes to main and 0.6.0-alpha release such that we can start testing it.
Amazing stuff 👏 Thanks a lot, Dan!
wow this marks the end of an era! and a new beginning. Excited to start improving things like |
No description provided.