-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
ts: Migrate vdom.js
to TypeScript
#26272
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zulipbot
added
buddy review
GSoC buddy review needed.
mentor review
GSoC mentor review needed.
labels
Jul 17, 2023
PIG208
reviewed
Jul 17, 2023
@@ -2,7 +2,26 @@ import _ from "lodash"; | |||
|
|||
import * as blueslip from "./blueslip"; | |||
|
|||
export function eq_array(a, b, eq) { | |||
type Equal<T> = (...args: T[]) => boolean; |
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.
eq
for Node
takes 1 argument, eq
for eq_array
takes 2 arguments. Let's type them separately to be more precise.
Added type annotations for variables, function params, and return values. Created custom types that help with clean type annotations. Notes on `attrs` field in custom `Option` type: `attrs` is an `Iterable` where each element is a pair of string, i.e a string array with two elements. `attrs` is tranformed into a `Map` at some point. `Map` constructor takes in `Iterable` object so has no problem unifying with `attrs`. However, at some point `attrs` is transfomed using `.map(...)` which is an array method, and `Iterable` does not support `.map(...)`. So at this point, I cast `attrs` into array before using `.map(...)` by this syntax: `[..attrs].map(...)`
zulipbot
added
integration review
Added by maintainers when a PR may be ready for integration.
and removed
buddy review
GSoC buddy review needed.
mentor review
GSoC mentor review needed.
labels
Jul 24, 2023
Merged, thanks @jychen630 and @PIG208! |
andersk
added
the
area: typescript migration
Issues for migrating Zulip to TypeScript
label
Oct 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: typescript migration
Issues for migrating Zulip to TypeScript
integration review
Added by maintainers when a PR may be ready for integration.
size: M
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added type annotations for variables, function params, and return values. Created custom types that help with clean type annotations.
Notes on
attrs
field in customOption
type:attrs
is anIterable
where each element is a pair of string, i.e a string array with two elements.attrs
is tranformed into aMap
at some point.Map
constructor takes inIterable
object so has no problem unifying withattrs
. However, at some pointattrs
is transfomed using.map(...)
which is an array method, andIterable
does not support.map(...)
. So at this point, I castattrs
into array before using.map(...)
by this syntax:[..attrs].map(...)
Much inference is inspired by
vdom.test.js
.Self-review checklist
(variable names, code reuse, readability, etc.).
Communicate decisions, questions, and potential concerns.
Individual commits are ready for review (see commit discipline).
Completed manual review and testing of the following: