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

Updated ExplorerPage to use static title field #5118

Closed
wants to merge 2 commits into from

Conversation

kwelch
Copy link

@kwelch kwelch commented Jan 4, 2016

Statics field was never used, I came with intent to remove it. I changed course when I noticed that this title matched the static.

Statics field was never used, I came with intent to remove it. I changed course when I noticed that this title matched the static.
@facebook-github-bot
Copy link
Contributor

By analyzing the blame information on this pull request, we identified @mkonicek, @foghina and @crm416 to be potential reviewers.

@facebook-github-bot
Copy link
Contributor

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at [email protected]. Thanks!

@@ -44,7 +44,7 @@ var ToolbarAndroidExample = React.createClass({
},
render: function() {
return (
<UIExplorerPage title="<ToolbarAndroid>">
<UIExplorerPage title={statics.title}>

Choose a reason for hiding this comment

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

no-undef: "statics" is not defined.

@facebook-github-bot
Copy link
Contributor

@kwelch updated the pull request.

@kwelch kwelch closed this Jan 5, 2016
@kwelch kwelch reopened this Jan 5, 2016
@astreet
Copy link
Contributor

astreet commented Jan 5, 2016

First off, thanks for the PR! However, it doesn't really make sense to me why we're updating exactly one example to be like this... I'd probably be ok with updating all of them, but really I don't think it's worth your time doing -- this isn't really much of an issue :)

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.

4 participants