Skip to content
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

made it possible to change filter placeholder text #780

Merged
merged 3 commits into from
Mar 16, 2018
Merged

made it possible to change filter placeholder text #780

merged 3 commits into from
Mar 16, 2018

Conversation

Saldivarcher
Copy link
Contributor

Griddle major version

1.11.0

Changes proposed in this pull request

Fixed one of the issues regarding #774, which is an easy change to filter place holder text

Why these changes are made

To be able to change the place holder text without creating a new component.

Are there tests?

Ran npm run test and it passed all tests.

@Saldivarcher Saldivarcher changed the title made it possible to change filter text made it possible to change filter place holder text Dec 21, 2017
@Saldivarcher Saldivarcher changed the title made it possible to change filter place holder text made it possible to change filter placeholder text Dec 21, 2017
Copy link
Contributor

@dahlbyk dahlbyk left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution! I've left a few suggestions, all pretty trivial.

@@ -767,6 +767,14 @@ storiesOf('Griddle main', module)
</Griddle>
)
})
.add('with Filter place-holder', () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you move this down into a new Filter section of stories, similar to the story for settingsToggle?

Copy link
Contributor Author

@Saldivarcher Saldivarcher Dec 23, 2017

Choose a reason for hiding this comment

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

Should I also move all the filter examples from the Griddle Main section, to this section?

@@ -40,6 +40,7 @@ export default {
textProperties: {
next: 'Next',
previous: 'Previous',
settingsToggle: 'Settings'
settingsToggle: 'Settings',
filterPlaceHolder: 'Filter'
Copy link
Contributor

Choose a reason for hiding this comment

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

  1. Can we rename this as filterPlaceholder since the attribute is placeholder not placeHolder?
  2. Maybe keep the list alphabetized?

@@ -5,7 +5,8 @@ class Filter extends Component {
static propTypes = {
setFilter: PropTypes.func,
style: PropTypes.object,
className: PropTypes.string
className: PropTypes.string,
text: PropTypes.string
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it make sense to rename this prop as placeholder, to align with the textProperties key and to make explicit how the value will be used?

Bonus points if you add a trailing comma.

@dahlbyk
Copy link
Contributor

dahlbyk commented Dec 23, 2017

@ryanlanciaux also, this includes a package-lock.json file. Have you specifically been avoiding including one (in which case we should add to .gitignore?

@dahlbyk
Copy link
Contributor

dahlbyk commented Dec 23, 2017

Changes look good to me. I'm ambivalent on relocating the other Filter story, as it really belongs in a Redux section.

@ryanlanciaux?

@Saldivarcher
Copy link
Contributor Author

@dahlbyk @ryanlanciaux I don't think that's a bad idea to put it into a redux section, along with the custom column chooser within the settings story.

@Saldivarcher
Copy link
Contributor Author

Saldivarcher commented Mar 15, 2018

Were these changes good, or should I fix them @dahlbyk? 😸

@dahlbyk dahlbyk merged commit dfd7131 into GriddleGriddle:master Mar 16, 2018
@dahlbyk
Copy link
Contributor

dahlbyk commented Mar 16, 2018

Sorry for the delay, @miguelsaldivar. All the maintainers are stretched pretty thin, but we do appreciate the contribution!

@Saldivarcher
Copy link
Contributor Author

No no, it's fine don't even worry 😄, I'll look for some other bugs I can fix to help you guys out!

@dahlbyk dahlbyk mentioned this pull request Aug 15, 2018
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