-
Notifications
You must be signed in to change notification settings - Fork 283
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
deps: upgrade to typescript 4.x #2990
Conversation
results.push(item instanceof Case ? item : new Case(item.value, item.actions)); | ||
}); | ||
return results; | ||
class CasesConverter implements Converter<Array<CaseInput | Case>, Case[]> { |
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.
I think this actually more accurately describes the converter. This fixes a compilation error as well.
9162426
to
388ac38
Compare
e76fcba
to
9de05af
Compare
388ac38
to
b6f5805
Compare
hi @joshgummersall About the version of antlr target. I have an idea that to use antlr4 and @types/antlr4 instead of the original antlr4ts which is not maintained in the future anymore. |
I'm hesitant to move to allowJs. I'm also not familiar with that package so I'll have to investigate. Are the types you mentioned not expressed in @types/antlr4? |
The @types/antlr4 just provide the types of the antlr SDK library without the types of the generated files(lexer/parser/listener/visitor). |
Got it. I'll investigate a little more tomorrow. Maybe we can figure out a reasonable way to generate some typings. |
512d9e5
to
062595e
Compare
062595e
to
0f91bc0
Compare
Speaking of typings, when this PR is ready to merge, let's cut a daily build prior to merge and ask the Southworks team working with Solutions to test the SDK built with They caught the typings issue last year due to different TypeScript versions being used for our SDK. |
8efef93
to
b4bf0dc
Compare
b4bf0dc
to
6c3de4a
Compare
502a9ce
to
bdd6927
Compare
@stevengum I've cut a build of this ( I do think we should cut a build once it lands and have Southworks test it, especially if they are doing more extensive testing than what I described. In the case that they are testing more extensively we should also codify that and run it as some kind of CI job. |
ee6855a
to
da59ea3
Compare
Admittedly a bikeshed moment, but was bothered by some opaque test failures. This makes the tests a lot more isolated, DRY, and generaly nicer to work with.
b9846bc
to
47b90b2
Compare
Note: rebased to clean up commit log. No code changes. |
Hi @stevengum & @joshgummersall, we successfully validated the build |
Fixes #1441
Note: it looks like our use of
antlr
doesn't play nicely with the newer Typescript compiler. In a few places,skipLibCheck
fixes the compilation errors. In others, unfortunately, it does not. I believeadaptive-expressions
and its derivatives were the only examples wheretypescript@3.5.3
is required.