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

Clarify naming expectation for glyph prop #2469

Merged
merged 1 commit into from
Feb 10, 2017

Conversation

sidewaysgravity
Copy link
Contributor

It was not immediately obvious to remove the prefix since we specify using the icon name with a link to bootstrap which does use the prefix. It was only after looking at the sample and my written code that I noticed the difference.

While its nothing major I feel that this just adds a bit of clarity to the naming convention.

It was not immediately obvious to remove the prefix since we specify using the icon name with a link to bootstrap which does use the prefix. It was only after looking at the sample and my written code that I noticed the difference.
@jquense
Copy link
Member

jquense commented Feb 10, 2017

LGTM thanks!

@taion taion merged commit fe0fd04 into react-bootstrap:master Feb 10, 2017
@sidewaysgravity
Copy link
Contributor Author

@jquense When looking through the documentation, It looked as if the docs were built off the annotations which is what I have updated. I noticed that the docs at https://react-bootstrap.github.io/ still don't show the updated description. Are those docs built and updated separate from the pull requests or was there something else that I needed to update for the change to show?

@jquense
Copy link
Member

jquense commented Feb 13, 2017

@sidewaysgravity the docs site isn't deployed automatically on a PR, we have to actually manually trigger a deploy for it. So no worries on your end, we jsut haven't pushed the update out yet.

@sidewaysgravity
Copy link
Contributor Author

@jquense Cool. No rush on it, I just wanted to make sure I didn't miss something.

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.

None yet

3 participants