Skip to content

[guide] [react] add comment about what JS standards are followed #1740

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 1 commit into from
Feb 22, 2018

Conversation

raunofreiberg
Copy link
Contributor

Seen a few pull requests for the React style guide that try to introduce features that aren't yet in stage >= 3 (static class fields for i.e), so I've decided to add a comment to the beginning of the guide. Not sure if this is the right place to put it, but here it is.

This disclaimer might help:

  1. give the community an idea what standards this guide is based on
  2. prevent redundant pull requests

Seen a few pull requests for the React style guide that try to introduce features that aren't yet in stage >= 3 (static class fields for i.e), so I've decided to add a comment to the beginning of the guide. Not sure if this is the right place to put it, but here it is.

This disclaimer might help:
1) give the community an idea what standards this guide is based on
2) prevent redundant pull requests
Copy link

@mariak4s mariak4s left a comment

Choose a reason for hiding this comment

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

very nice comment 10/10

react/README.md Outdated
@@ -2,6 +2,9 @@

*A mostly reasonable approach to React and JSX*

This style guide is based on the standards that are currently prevalent in JavaScript or proposals in stage 3 or greater.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's qualify this by saying it's case-by-case; async/await is still prohibited by this guide which is stage 4, as are class instance fields which are stage 3.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fair point. I've went ahead and improved the general idea of this comment by amending the last commit. Let me know how it looks like now.

@raunofreiberg raunofreiberg force-pushed the patch-1 branch 5 times, most recently from b9d080b to 8ad7c4c Compare February 22, 2018 00:17
Copy link
Collaborator

@ljharb ljharb left a comment

Choose a reason for hiding this comment

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

Thanks, looks great!

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.

3 participants