-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Yet More Vue Typing Error Fixes #19680
Conversation
a52be92
to
efc3171
Compare
I think after this PR all the remaining errors have an issue or a PR. Here are the 13 and links.
|
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.
Awesome! Thank you so much!
@dannon mentioned he wanted to check something during the meeting, otherwise, I think it is ready to merge.
…ary. Fixes some vue-tsc errors.
Looks serious - maybe should be backported.
... this is so a HistoryDetailed IS_A Item. This fixes a Vue TSC error.
Build an client-side object closer to what is generated in Python so the types align.
Cleans up Vue TSC errors in Node.vue.
@davelopez thanks for the review; looking now. The thing I wanted to track down was that I thought I saw a loosening of something to I'll give the rest a quick look. Thanks again for the dedication to this @jmchilton |
@dannon Possible - I took a couple different stabs at hardening the object store selection typing - sort of get it working and then get it right approach. It was probably in there. |
@davelopez has done a lot of review of #19663 so I thought I would cleanup that branch and rebase it until those fixes are ready and open a new PR with the next set of fixes on top of those.
How to test the changes?
(Select all options that apply)
License