Skip to content

Conversation

@darkwing
Copy link
Contributor

Description:
Fixes #1129

I suspect this one will require much more work. I've run tests and all passes but things to consider:

  • Is this a breaking change moving forward where API docs must be updated? Is it work the breaking change?
  • What other components may need updating to accommodate an array instead of a NodeList?

function selectorAllParse (value) {
if (!value) { return null; }
if (typeof value !== 'string') { return value; }
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should value also be wrapped in Array.from()? What is the use case? In case a NodeList instance is passed in?

Copy link
Member

Choose a reason for hiding this comment

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

We might want to return [] in the cases above?

Copy link
Member

Choose a reason for hiding this comment

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

I think the first case may be for {default: ''} so we don't need to run that.

The second case is if an array or NodeList is passed in yeah.

@ngokevin
Copy link
Member

looks good to me

@dmarcos dmarcos merged commit cce05b3 into aframevr:master Jul 19, 2016
@ngokevin
Copy link
Member

@darkwing thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

3 participants