Add OpenLayers typings and use to fix type mismatches #247
Conversation
This file contains 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
Neonox31
force-pushed
the
next
branch
11 times, most recently
from
b83fbe4
to
83cf6f5
Compare
jeremy-eychenne
force-pushed
the
next
branch
3 times, most recently
from
7cb331d
to
a70ba9c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a redo of #244, rebased on top of the latest
nextbranch to bring in the changes to support Angular 8 and OpenLayers 6.I understand if this is adding more type annotations than this project would like to support, but of particular interest to me is getting the imports fixed in the few cases were they were wrong:
I can open a smaller-scope pull request with just those changes if that would be preferred.