Merged
Conversation
…grations, also createType option
This was referenced Apr 16, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
addresses not creating or running migrations when an app / topic is created, which was causing the generated app to crash on visting
/dogsnow when a user creates an app, they are prompted as to whether:
a migration can also now be created from
createType, and it will be created in the appdb/migrationsfolder.there is minimal error handling for if the user already has a database existing with the same name as generated by
createApp(i.e.${appName}_development), but this could probably be improved, as could error handling for no Postgres installed / running or other errors - a ticket to be made for this.