-
Notifications
You must be signed in to change notification settings - Fork 3
User subscription #255
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
User subscription #255
Conversation
|
I like the choice to include the individual plan and mark it "coming soon". |
| isFetching ? ( | ||
| <> | ||
| <Grid item> | ||
| <Skeleton animation="wave" width={300} height={200} /> |
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.
Had to look this up -- very cool.
| PXT_HEX_URL: JSON.stringify(process.env.PXT_HEX_URL | ||
| || 'https://rovercode-pxt.s3.us-east-2.amazonaws.com/alpha/rovercode.hex'), | ||
| SAVE_DEBOUNCE_TIME: JSON.stringify(process.env.SAVE_DEBOUNCE_TIME), | ||
| SUBSCRIPTION_SERVICE: JSON.stringify(process.env.SUBSCRIPTION_SERVICE |
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 was going to suggest that we define this per branch in the .travis.yml deploys, but I guess that's not a thing. We can just set them in the Travis build settings in their web interface.
hbradio
left a comment
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.
Awesome!
Displays the current plan information for the user. Sets up the logic to handle using access codes to activate the user's plan. Sets individual plans to


Coming soon: