Skip to content

Conversation

Gregcop1
Copy link
Contributor

@Gregcop1 Gregcop1 commented Apr 3, 2018

No description provided.

@coveralls
Copy link

coveralls commented Apr 3, 2018

Coverage Status

Coverage remained the same at 98.534% when pulling 582ee1c on feat-clear-on-select into 4fc88fb on master.

@mrchief
Copy link
Collaborator

mrchief commented Apr 3, 2018

Looks good. We should add this options to Options story under docs as well.

@Gregcop1
Copy link
Contributor Author

Gregcop1 commented Apr 3, 2018

So how do you want to proceed. We merge the first commit then I do an exemple in codesandbox and we merge again? Or do we blindly hope my second commit will work? ;)

@mrchief
Copy link
Collaborator

mrchief commented Apr 3, 2018

I use the options story as an end user test (this way we don’t leave anything to fate).

Add an option there, test out if the component does what it’s supposed to and if everything checks out, I know I’m good to go.

Bonus, we get free documentation with real live examples.

Codesandbox is good but I don’t think we need to create one for every little flag. People can play with the base sandbox or can checkout docs for examples.

Makes sense?

Oh wait, is the options story part of the partial state PR? If so, I guess I’ll have to merge it soon. I was hoping codeclimate support can fix the issues first but maybe I’ll skip it for that PR (yarn lint checks out so I know its GTG). I’m on a phone so I’ll let you know more tonight.

@Gregcop1
Copy link
Contributor Author

Gregcop1 commented Apr 4, 2018

I don't see the options entry in my doc so I think it's in your current PR. (I was asking myself how you do local test with this process but now I know. :))
I review your PR right know and will update mine after your merge

@Gregcop1 Gregcop1 force-pushed the feat-clear-on-select branch from c0f308d to 9c37377 Compare April 5, 2018 12:52
@Gregcop1
Copy link
Contributor Author

Gregcop1 commented Apr 5, 2018

@mrchief I've updated the "story" part

src/index.js Outdated
})
if (this.props.simpleSelect) this.resetSearch()
this.notifyChange(this.treeManager.getNodeById(id), tags)
if (this.props.clearSearchOnChange) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

This can probably be combined with if (this.props.simpleSelect)

@mrchief
Copy link
Collaborator

mrchief commented Apr 5, 2018

Would you mind running yarn build:docs and checking in the updated docs/bundle.js? Also note a minor comment.

@Gregcop1
Copy link
Contributor Author

Gregcop1 commented Apr 5, 2018

What do you want me to check in docs/bundle.js? It mentions clearSearchOnChange but I don't know if you want me to check something else

Copy link
Collaborator

@mrchief mrchief left a comment

Choose a reason for hiding this comment

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

👍

@mrchief mrchief merged commit 3b0753a into master Apr 5, 2018
@mrchief mrchief deleted the feat-clear-on-select branch April 5, 2018 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants