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
feat(core): infer property type from default value #4150
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
B4nan
force-pushed
the
default-value-inference
branch
from
March 19, 2023 18:05
10fd262
to
6bdc3a1
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## v6 #4150 +/- ##
==========================================
+ Coverage 99.56% 99.58% +0.01%
==========================================
Files 217 217
Lines 13945 13950 +5
Branches 3190 3193 +3
==========================================
+ Hits 13885 13892 +7
+ Misses 56 54 -2
Partials 4 4
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
B4nan
added a commit
that referenced
this pull request
Mar 19, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Apr 6, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Apr 10, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Apr 12, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Apr 26, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
jsprw
pushed a commit
to jsprw/mikro-orm-full-text-operators
that referenced
this pull request
May 7, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes mikro-orm#4060
B4nan
added a commit
that referenced
this pull request
May 14, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
May 14, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
May 24, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
May 26, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Jun 11, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Sep 10, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Sep 20, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Sep 24, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Sep 30, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Oct 2, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Oct 17, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Oct 21, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Oct 25, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Nov 2, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
B4nan
added a commit
that referenced
this pull request
Nov 5, 2023
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g. `created = new Date` instead of `created: Data = new Date`. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, so `created = new Date` will work fine. Closes #4060
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type inference with reflect-metadata fails when a runtime value is used without an explicit type annotation, e.g.
created = new Date
instead ofcreated: Data = new Date
. This PR infers the default value from the property initializer (if possible) and uses its type in this automatically, socreated = new Date
will work fine.Closes #4060