Skip to content

refactor(selection-model): avoid unnecessary null checks in change event #9850

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

Merged
merged 1 commit into from
Feb 13, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Feb 8, 2018

  • Makes the added and removed properties on the SelectionChange event required since they're guaranteed to be an empty array. This makes it more convenient to consume, because it avoids having to null check them every time.
  • Turns the SelectionChange into an interface to reduce the amount of code being generated.

* Makes the `added` and `removed` properties on the `SelectionChange` event required since they're guaranteed to be an empty array. This makes it more convenient to consume, because it avoids having to null check them every time.
* Turns the `SelectionChange` into an interface to reduce the amount of code being generated.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 8, 2018
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

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Feb 9, 2018
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Feb 9, 2018
@jelbourn jelbourn merged commit 0db1795 into angular:master Feb 13, 2018
andrewseguin pushed a commit that referenced this pull request Feb 20, 2018
…ent (#9850)

* Makes the `added` and `removed` properties on the `SelectionChange` event required since they're guaranteed to be an empty array. This makes it more convenient to consume, because it avoids having to null check them every time.
* Turns the `SelectionChange` into an interface to reduce the amount of code being generated.
@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 Sep 8, 2019
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants