Open
Conversation
Instead of blacklisting unwanted files for npm packing, whitelist wanted ones. Blacklisting, by nature, can easily result in unwanted files getting packed.
We now have: - a base tsconfig for project wide settings - a new tsconfig for the spec files, these were not tested before - a tsconfig for the app/src only - a solution style tsconfig file for IDEs
The type check could not deal with complex types such as `Array<string> | null`. This example is only a problem with `strictNullChecks` enabled.
This should improve safety as explained in https://eslint.org/docs/rules/no-prototype-builtins.
Co-authored-by: Alessandro Moscatelli <alessandro.moscatelli@visiontech.cloud>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
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.
No description provided.