new BUGs, reformatting again

This commit is contained in:
2020-12-31 12:33:56 +11:00
parent ddfd0b878b
commit cf344d6439
2 changed files with 18 additions and 4 deletions

13
BUGs
View File

@@ -1,3 +1,4 @@
#### BUGS
BUG-1: loan card is not in right div anymore (since series stuff?) BUG-1: loan card is not in right div anymore (since series stuff?)
http://mara.ddp.net:5000/book/1513 http://mara.ddp.net:5000/book/1513
@@ -14,3 +15,15 @@ BUG-6 author,series, etc. do not have explicit ordering like sub-books... sort o
BUG-7 if you remove a series from a book, it won't appear in the series drop-down if it is the first 'missing' book in that series -- either reset the list, or show all series always? BUG-7 if you remove a series from a book, it won't appear in the series drop-down if it is the first 'missing' book in that series -- either reset the list, or show all series always?
BUG-8 if you add a sub-book, then fail to validate (say no genre), then it takes you back, you click a genre (BUT it has lost th eparent association), so it adds a book, not a sub-book BUG-8 if you add a sub-book, then fail to validate (say no genre), then it takes you back, you click a genre (BUT it has lost th eparent association), so it adds a book, not a sub-book
### SHOWSTOPPERS: sub book issues, did the following steps:
http://mara.ddp.net:5000/series/112
http://mara.ddp.net:5000/book/1282 (Mavin Manyshaped)
Add Sub-book -> BUG-9
then to test above, I:
created a new book
created a new sub-book
Saved it, and it added to Mavin Manyshaped parent book, not the new book -> BUG 10
BUG-9 raw DB error as blurb field is undefined -- seems the hidden fields at bottom of form are missing
BUG-10 raw DB error as blurb field is undefined -- we are not trapping this sort of DB error?
BUG-11 added to wrong parent book

9
README
View File

@@ -23,13 +23,14 @@ pip3 install --user flask sqlalchemy flask-sqlalchemy flask-marshmallow SQLAlche
# run the web server by: # run the web server by:
python3 main.py python3 main.py
### MAYBE:
when moving a book in a series (which is part of 2 series), do we pop-up
offer to move parent/child series orders as well to match (think Thomas Covenant)
### Remember: ### Remember:
MUST use form.errors when we have a validator that is fancier than not empty (year_published in book and num_books in series SO FAR) MUST use form.errors when we have a validator that is fancier than not empty (year_published in book and num_books in series SO FAR)
#### MAYBEs:
MAYBE-1: when moving a book in a series (which is part of 2 series), do we pop-up offer to move parent/child series orders as well to match (think Thomas Covenant)
#### TODOS:
TODO-1 consider created/modifed for all fields? but mostly are they set via ORM for new books? TODO-1 consider created/modifed for all fields? but mostly are they set via ORM for new books?
* No, not being set... * No, not being set...
TODO-2 need to delete 1 sub_book from book TODO-2 need to delete 1 sub_book from book