Skip to content

Conversation

crisbeto
Copy link
Member

The Google Maps marker is currently marked as a component, but it isn't using any component features. These changes turn it into a directive since it also allows consumers to apply it on elements that are components.

Note for reviewer: I don't know whether we should mark this as a breaking change, because on one hand the public API is the same, but on the other it could affect consumers that have implicit template references.

cc @mbehrlich

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Jun 14, 2020
@crisbeto crisbeto requested a review from a team as a code owner June 14, 2020 14:07
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 14, 2020
The Google Maps marker is currently marked as a component, but it isn't using any component features. These changes turn it into a directive since it also allows consumers to apply it on elements that are components.
@crisbeto crisbeto force-pushed the map-marker-directive branch from 5f066c9 to e0ad72d Compare June 14, 2020 20:21
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I wouldn't think this to be a breaking change since it uses an element selector

@jelbourn jelbourn added lgtm action: merge The PR is ready for merge by the caretaker labels Jun 16, 2020
@jelbourn jelbourn merged commit fcbcfd7 into angular:master Jun 29, 2020
jelbourn pushed a commit that referenced this pull request Jun 29, 2020
The Google Maps marker is currently marked as a component, but it isn't using any component features. These changes turn it into a directive since it also allows consumers to apply it on elements that are components.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants