Skip to content
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.

Tidy up consistency for singular and multiple classes #740

Merged
merged 1 commit into from
Nov 2, 2017

Conversation

matt-gadd
Copy link
Contributor

Type: bug

The following has been addressed in the PR:

  • There is a related issue
  • All code matches the style guide
  • Unit or Functional tests are included in the PR

Description:

The typings for a singular classname did not support null, while the multiple variance did in Themed. In VirtualDomProperties classes supported null across both, but the array version supported undefined also. The typings are now consistent across everything.

Functionally, passing null in an array to this.theme filtered it, while passing null singularly would log a warning. The functionality is now to not warn or filter consistently across both, as the filtering is done in vdom anyway.

Copy link
Member

@agubler agubler left a comment

Choose a reason for hiding this comment

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

Awesome even cleaner and less lines of codes

Copy link
Member

@kitsonk kitsonk left a comment

Choose a reason for hiding this comment

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

Note to self, need to update that in test-extras

@matt-gadd matt-gadd merged commit 6bbf5a8 into dojo:master Nov 2, 2017
@dylans dylans added this to the beta.4 milestone Jan 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants