Closed
Conversation
those three break noImplicitAny (TS7006) and I can't find some meaningful documentation for the first two so I chose to remove them from these typings
Contributor
|
Fixed in #602, should be closed. |
Contributor
|
@j2L4e Could you resolve the conflict? Thanks. |
Member
|
Fixed via #602 and released as v2.1.4 |
daffl
added a commit
that referenced
this pull request
Aug 29, 2018
daffl
added a commit
that referenced
this pull request
Aug 29, 2018
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
4 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.
those three break noImplicitAny (TS7006) and I can't find some meaningful documentation for the first two so I chose to remove them from these typings
Summary
(If you have not already please refer to the contributing guideline as described
here)
typescript compilation with noImplicitAny flag set
If so, please mention them to keep the conversations linked together.
Other Information
If there's anything else that's important and relevant to your pull
request, mention that information here. This could include
benchmarks, or other information.
Your PR will be reviewed by a core team member and they will work with you to get your changes merged in a timely manner. If merged your PR will automatically be added to the changelog in the next release.
If your changes involve documentation updates please mention that and link the appropriate PR in feathers-docs.
Thanks for contributing to Feathers! ❤️