Skip to content

Gpinto lookup modifications #45

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
Oct 29, 2015
Merged

Conversation

xanthousphoenix
Copy link
Contributor

Major things:

  • added onItemUnselect callback for when the item gets deselected
  • added a prop called boldRegex to be used for bolding the item text
  • fixed the bolding regex default behavior (it wasn't escaping it)

Minor things:

  • deleted empty lines
  • make coding style more consistent where I noticed it

@madpotato

@@ -17,16 +18,19 @@ class Item extends React.Component {
}

componentWillReceiveProps(nextProps){
if(nextProps.isActive !== this.props.isActive && nextProps.isActive === true){
if (nextProps.isActive !== this.props.isActive && nextProps.isActive === true) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The sublime text 3 babel javascript syntax highlighter treats if(<condition){<code>} as if if was a function call. if (<condition>) {<code>} highlights it as a conditional instead. Let me know if we want to use the first way anyways.

ivanbogdanov pushed a commit that referenced this pull request Oct 29, 2015
@ivanbogdanov ivanbogdanov merged commit 18bae9a into master Oct 29, 2015
@donnieberg donnieberg deleted the gpinto_lookup_modifications branch December 17, 2015 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants