Bug | null dropping alias annotations
See original GitHub issue/**
* @minimum 1
* @TJS-type integer
*/
type natural = number;
interface Schema {
id: natural | null;
}
This results in json for a plain unannotated number being generated. With @nullable, it does work correctly.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Null annotations are extremely hard to use in an existing project
I was trying to use null annotations in o.e.jdt.ui but it becomes extremely hard very quickly. Actually I should say it is impossible...
Read more >Spring data JPA: getting No aliases found in result tuple! error ...
Searching for this error shows spring data jpa: No aliases found in result tuple! Make sure your query defines aliases which says that...
Read more >Path-Sensitive and Alias-Aware Typestate Analysis for ...
However, each OS inevitably has bugs, as it is quite large and complex. Even a simple OS bug. (such as null-pointer dereference) can...
Read more >Full Text Bug Listing - Red Hat Bugzilla
Summary: Coverity-detected defect: null pointer dereferences in uri.c ... don't check g_strdup arg for NULL 2458810 Drop superfluous conditionals around ...
Read more >Opaque Type Aliases - Scala 3 - EPFL
object MyMath: opaque type Logarithm = Double object Logarithm: // These are the two ways to lift to the Logarithm type def apply(d:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Becomes:
While I would expect:
same for me,–strictNullChecks not work