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

Move constants to top level directory #53

Merged
merged 1 commit into from
Sep 15, 2016

Conversation

majapw
Copy link
Collaborator

@majapw majapw commented Sep 1, 2016

This is to allow for import { START_DATE END_DATE } from 'react-dates/constants'; and it makes sense for it not to need transpilation since the file is literally a collection of strings. However, it is breaking.

@majapw majapw added the semver-major: breaking change A non-backwards-compatible change; anything that breaks code - including adding a peerDep. label Sep 1, 2016
@majapw majapw force-pushed the move-constants-to-top-level-directory branch 4 times, most recently from 7cf44f0 to b64d0c2 Compare September 1, 2016 23:13
@ljharb
Copy link
Member

ljharb commented Sep 2, 2016

LGTM - looks like you'll need to update some paths in tests too

@majapw
Copy link
Collaborator Author

majapw commented Sep 2, 2016

Oops! I totally thought I had.

@majapw majapw force-pushed the move-constants-to-top-level-directory branch 2 times, most recently from ae3dae3 to bfeeef0 Compare September 6, 2016 18:36
@majapw majapw force-pushed the move-constants-to-top-level-directory branch from bfeeef0 to 2609919 Compare September 13, 2016 14:57
This should allow consumers to do `import { START_DATE, END_DATE } from 'react-dates/constants';` which is ideal
@majapw majapw force-pushed the move-constants-to-top-level-directory branch from 2609919 to 0e45890 Compare September 13, 2016 18:20
@majapw majapw merged commit 26ced4d into master Sep 15, 2016
@majapw majapw deleted the move-constants-to-top-level-directory branch September 15, 2016 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-major: breaking change A non-backwards-compatible change; anything that breaks code - including adding a peerDep.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants