-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Map markers #16964
Map markers #16964
Conversation
packages.bzl
Outdated
@@ -82,6 +82,7 @@ MATERIAL_SCSS_LIBS = [ | |||
|
|||
GOOGLE_MAPS_PACKAGES = [ | |||
"google-map", | |||
"google-map-marker", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be a separate sub-package; I would just make it a sub-directory of google-map
that is in the same build unit (e.g. no new tsconfig, NgModule, SystemJS config BUILD file, etc.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about this for awhile and I think you're right, that it should be in the same module. However, if that's the case, then we also shouldn't have a separate module for google-map. In other words, we should just have '@angular/google-maps' instead of '@angular/google-maps/google-map'. That's a pretty big refactor though, do you think it should be done in the same pull request?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That will be fine in a follow-up. I never actually realized it wasn't one main module for the whole thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, that sounds good. For this one, I will connect google-map-marker to the google-map module, and in the subsequent cl, I will have both of them be in a google-maps module.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran into some unexpected problems having google-map remain a separate subpackage but integrating map-marker. So, to avoid having to double my work, I decided to just combine everything into one package in this pr. It makes this already very large pr even bigger, but it should correct the build failures you saw.
847c474
to
ee061b4
Compare
@mbehrlich looks like there's a build failure on CI |
Add a google-map-marker component that when used as a child to a google-map component, will display a marker on the map.
Add tests for the google-map-marker component.
Add tests to Google Map marker component.
Fix bug with demo bazel file and with fake data for marker test.
Make various fixes internal cleanup fixes. Change google-map-marker to map-marker. Use QueryList's changes property instead of a setter for ContentChildren.
Fix type bug with map marker tests.
Refactor google-maps module to have a single entry-point, @angular/google-maps, instead of a separate one for every component.
Fix formatting on google maps module.
ee061b4
to
c574a10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
CI failure looks like you're just missing a |
Add GoogleMap and MapMarker components to index for the google maps module.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Adds google-map-marker component.