Use classNameBindings
instead of writing into classNames
#117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partially closes #116
Directly muting
classNames
is slated to be disallowed in the next version of Ember, and thus the one instance where we were [doing this in ourtable-columns
component] seems to be the culprit for our current CI failures (testing againstember-beta
andember-canary
).This PR updates the component so that instead of pushing into
classNames
inside ofinit
, we just compute thecolumnType
-dependent class as aclassNameBinding
.