-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
51 lines (41 loc) · 1.57 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Extension of Database final Project:
A trip planner database was implemented in MySQL, with a command-line controller app implemented in python.
This repository contains those files, as well as a React-based frontend under construction
yarn start -> runs react front-end
yarn start-api -> runs flask api
TODO:
* Collection REMOVE
* use useGet hook?
* consolidate Collectionspecs and detailspecs
- style expanded table
- new data is not automatically loaded on update
- save place with pagination on update?
- test table with more requests
- handle HTTP errors
- handle DB fetch errors
- add error reporting
- personalize
PROBLEMS:
many inputs can be negative
NOTES:
initial component structure was
TableWrapper -> Table (API call)
-> Inputs -> RowAdder -> Table (input data)
with Inputs being selectable based on TableWrapper type and RowAdder it's table being generic
Could not dynamically pattern the inputs, and could not pass specifications from context without a ton of data in context
restructured to:
Inputs -> TableFetcher -> Table (API call)
-> RowAdder -> Table (input data)
further restructured to:
CRUDPanel -> InputForm -> Inputs
-> InputForm -> Inputs
-> DelteTable
-> CRUDButtons
-> TableHeader
-> Table
-> TableHeader
^TableContext^ provides specific API and header data
Table and TableHeader are all HTML, all state logic is in CRUDPanel
replaced PyMySQL backend with SQLAlchemy
cannot tell if automapper is worth it
the saga of checkboxes, radio buttons, and multiselect