-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
update project creation #5849
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
update project creation #5849
Conversation
Generated by 🚫 danger |
8dfacfb to
6d17794
Compare
7cb0966 to
f504e4d
Compare
53e2288 to
57eddd0
Compare
|
interested on UX + look+feel feedback as well! |
|
This looks good! A couple things I noticed:
I guess its possible that 1 is desired behavior because maybe people will want to configure their project for another platform and 2 is desired because we don't want to distract people from the configuration process with other options. Not sure how likely people are to go through the flow and go back to configuration. Overall it looks much better than the django view, though - I like it. |
|
I'm curious if it's safe to remove the old django view the way I did or if there's some complication i'm missing |
|
i'lll widen it! katie also mentioned some header stuff but i want to leave that off for a next pass along with some of billy's comments |
c32918a to
3191dfe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use the OrganizationState mixin here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't react-router provide this as a prop?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you might be right - it's also used as context all over though ;/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you grep for this.props.location it seems to be used more than this.context.location
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no change needed here, but thoughts on adding eslint rule for preferring shorthand?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
initial impression is no but I could be convinced otherwise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I've given people this feedback repeatedly, if we can automate it, let's.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we move this into render and is cloneElement needed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
: is still inside of t()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you must have been eating your fish eyes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I think it's a bit cleaner if we just invoke the method here (and more consistent w/ codebase)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:( this is cheekier. but you're right.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OrganizationState
1e8ca44 to
eb6605c
Compare
2333efa to
6050f19
Compare
fix percy fix acceptance tests
padding and cleanup move padding nvm about this formatting thing
6050f19 to
dd028d5
Compare
| }, | ||
|
|
||
| contextTypes: { | ||
| organization: SentryTypes.Organization, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
|
||
| const newProject = React.createClass({ | ||
| contextTypes: { | ||
| organization: SentryTypes.Organization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OrganizationState mixin
db63849 to
f84d49a
Compare



This PR replaces project creation with a new react view that captures platform intent and re-uses components from the onboarding view. it also removes the old django view and moves the tests to jest and acceptance
https://media.giphy.com/media/xUPJUs84cSrQC2USVW/giphy.gif