Skip to content
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

feat: Angular 10 Support #256

Closed
gongAll opened this issue Jul 31, 2020 · 4 comments · Fixed by #272
Closed

feat: Angular 10 Support #256

gongAll opened this issue Jul 31, 2020 · 4 comments · Fixed by #272

Comments

@gongAll
Copy link

gongAll commented Jul 31, 2020

When I upgrade my project to Angular 10 I get warning messages related to lack of support from ngx-openlayers to angular 10.
Please update ngx-openlayers package to support Angular 10.

@gongAll
Copy link
Author

gongAll commented Aug 4, 2020

So... any news regarding this issue? @quentin-ol @Neonox31 @davinkevin

@olierxleben
Copy link

I have created a new Angular application and was able to load the example from readme file. What does not work? Angular 10.1.6

@ShaiBarak
Copy link

ShaiBarak commented Nov 15, 2020

Also happen to me... (Angular 10.1.6 and Angular 10.2)
There's a lot of messages, for example:
Can't bind to 'ngForOf' since it isn't a known property of 'aol-feature'.

  1. If 'aol-source-vector' is an Angular component, then verify that it is part of this module.
  2. If 'aol-source-vector' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
  3. If 'aol-geometry-point' is an Angular component, then verify that it is part of this module.
  4. If 'aol-geometry-point' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.

@jeremy-eychenne
Copy link
Collaborator

Hi, PR 272 created to adress this issue. Do not hesitate to add feedback in PR if needed.

@jeremy-eychenne jeremy-eychenne linked a pull request Apr 11, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants