[go: up one dir, main page]

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

indicate file name requried for static file #4291

Merged
merged 2 commits into from
Jul 13, 2015
Merged

indicate file name requried for static file #4291

merged 2 commits into from
Jul 13, 2015

Conversation

rwoodnz
Copy link
Contributor
@rwoodnz rwoodnz commented Jul 5, 2015

the text doesn't say explicitly to call your file comments.json, nor to put it in the public directory.

the text doesn't say explicitly to call your file comments.json, nor to put it in the public directory.
@facebook-github-bot
Copy link

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 cla@fb.com. Thanks!

@@ -374,7 +374,7 @@ var CommentBox = React.createClass({
`getInitialState()` executes exactly once during the lifecycle of the component and sets up the initial state of the component.

#### Updating state
When the component is first created, we want to GET some JSON from the server and update the state to reflect the latest data. In a real application this would be a dynamic endpoint, but for this example, we will use a static JSON file to keep things simple:
When the component is first created, we want to GET some JSON from the server and update the state to reflect the latest data. In a real application this would be a dynamic endpoint, but for this example we will keep things simple by creating a static JSON file public/comments.json containing the array of comments:

```javascript
// tutorial13.json
Copy link
Contributor

Choose a reason for hiding this comment

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

It seems weird to call it tutorial13.json if everyone expects it to be comments.json. @spicyj @zpao, is there a reason this comment doesn't say comments.json.

Copy link
Member

Choose a reason for hiding this comment

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

The tutorial is broken into steps with file names to match (eg tutorial13.js would not actually be named that on disk, just used to indicate the step of the tutorial). Honestly we could probably get rid of those comments entirely.

@jimfb
Copy link
Contributor
jimfb commented Jul 5, 2015

Seems reasonable to me.

Also, @rwoodnz can you sign the CLA so we can merge? You know, lawyers :/

@rwoodnz
Copy link
Contributor Author
rwoodnz commented Jul 6, 2015

@jimfb. Cheers, yep I did the CLA. If I go to it now I get an error saying my email has already been used for it. [UPDATE have emailed the CLA address - looks like I hit agree without entering my github name]

@jimfb
Copy link
Contributor
jimfb commented Jul 6, 2015

RE CLA: Well, that's annoying. I found your record in the CLA database, but there is no github account attached to the record. I'll try to figure out the CLA situation on our end and ping you when I've figured out next steps.

@rwoodnz
Copy link
Contributor Author
rwoodnz commented Jul 6, 2015

Yep. My apologies on that one. Rushed through it and hit agree without filling in the box. After that you can't do it again.

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@jimfb
Copy link
Contributor
jimfb commented Jul 7, 2015

Ok, CLA situation has been solved. @rwoodnz, if you can amend your commit to put the public/comments.json in backticks (the key just above the escape key, , so it becomes public/comments.json`), I think we'll be ready to merge.

zpao added a commit that referenced this pull request Jul 13, 2015
indicate file name requried for static file
@zpao zpao merged commit e9b3974 into facebook:master Jul 13, 2015
@zpao
Copy link
Member
zpao commented Jul 13, 2015

👍

@fredericksilva
Copy link

👍

zpao added a commit that referenced this pull request Jul 17, 2015
indicate file name requried for static file
(cherry picked from commit e9b3974)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants