-
Notifications
You must be signed in to change notification settings - Fork 30
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
TypeScript issues #7
Comments
Sure, I am also integrating a tslint step in the buid with very strict
rules, I will probably commit it with the pdf417 code.
sâm., 11 nov. 2017, 23:01 Adrien Gibrat <notifications@github.com> a scris:
… I use zxing-typescript in a Typescript project with some strict compiler
options
{
"compilerOptions": {
"noImplicitAny": true,
"strictNullChecks": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"allowUnreachableCode": false,...
}
and I can't compile ;)
Are you open to PR to enforce stricter typescript rules ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#7>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA9uLbqo9ME4UcI9kUCRySQSM2JGHycXks5s1gsjgaJpZM4Qaooh>
.
|
Curious, did you ever do this? |
No sorry, there was a lot of development on a fork, where some improvements were mede. Unfortunately no pd417. |
I'm actually more interested in the strict compiler options, not pdf417 :) did those get enabled in that fork? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use zxing-typescript in a Typescript project with some strict compiler options
and I can't compile ;)
Are you open to PR to enforce stricter typescript rules ?
The text was updated successfully, but these errors were encountered: