Skip to content

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 1, 2018

Currently if, by any chance, assigns a negative number to the cols of a grid list, they'll get a cryptic error like Invalid array length, because down-the-line we use that number to create an array. These changes ensure that the value is always a positive number.

Currently if, by any chance, assigns a negative number to the `cols` of a grid list, they'll get a cryptic error like `Invalid array length`, because down-the-line we use that number to create an array. These changes ensure that the value is always a positive number.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Sep 1, 2018
@crisbeto crisbeto requested a review from jelbourn as a code owner September 1, 2018 15:25
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 1, 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 labels Sep 4, 2018
@jelbourn jelbourn merged commit cfb83a0 into angular:master Sep 11, 2018
jelbourn pushed a commit that referenced this pull request Sep 11, 2018
Currently if, by any chance, assigns a negative number to the `cols` of a grid list, they'll get a cryptic error like `Invalid array length`, because down-the-line we use that number to create an array. These changes ensure that the value is always a positive number.
@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 9, 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