Skip to content

Apply column visibility properly #5304

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 2 commits into from
Jun 24, 2016
Merged

Apply column visibility properly #5304

merged 2 commits into from
Jun 24, 2016

Conversation

conner-fallone
Copy link
Contributor

This fix removes an unneeded additional function when setting
column visibility. Since both functions were of the same
priority level, it was possible that the visibility that
was passed in would be overwritten with the default value of
true under certain circumstances. There was really no need
for two functions, as this default behavior can be accomplished
in one. This fixes the following issue: #5303

This fix removes an unneeded additional function when setting
column visibility. Since both functions were of the same
priority level, it was possible that the visibility that
was passed in would be overwritten with the default value of
true under certain circumstances. There was really no need
for two functions, as this default behavior can be accomplished
in one.
@AgDude AgDude merged commit 47c305e into angular-ui:master Jun 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants