Be explicit with create_admin function and tables= that we're not creating them, but registering them#460
Conversation
A more exact overview of what adding tables to the `create_admin` function does for beginners. Current `agsi new` cli example (in my opinion) isn't quite clear enough right now. 1. Add named argument to example 2. Add endpoint docs for `tables=`
|
This PR has been marked as stale because it has been open for 30 days with no activity. Are there any blockers, or should this be closed? |
|
@dantownsend I don't think this additional explanation is necessary as I think it's clear from the existing docs how create_admin (same for every other supported web framework) should be used. If you think this is useful, please merge this, if not, please close this PR. |
|
@sinisaos @dantownsend I think the issue I originally had was the example code on the page you linked to imports but doesn't create the tables and I assumed that function did it for you. Perhaps adding that to the example code would prevent the confusion. |
|
This PR has been marked as stale because it has been open for 30 days with no activity. Are there any blockers, or should this be closed? |
2 participants
A more exact overview of what adding tables to the
create_adminfunction does for beginners. The particular wording can be different if you prefer, but "add" in my experience (as you're using migrations inagsi newfor Piccolo ORM) can be confused with "create" (as increate_db_tables). Will also eventually slightly rewrite the "Getting started guide" foragsi new(will explain later).tables=Fixes piccolo-orm/piccolo#1276