-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathTODO
82 lines (59 loc) · 2.8 KB
/
TODO
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
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
* Next up:
- Make chrome extension notice when we've already imported a page.
- Make chrome extension "helper" view
- Improve autoparsing
-> Build proper testing framework for looking at import and parser w/o having
to wait for extension reloads
-> Test our node address handler -- it seems like we're managing to double
or triple import the same stuff when automatically parsing, and if we
could clear that up, it would be much better.
- Consider automated test of recipe editing -- it seems really easy to
screw up the state handling so the save/revert buttons don't show
up. (speaking of - we broke recipe editing state updates again
somehow???) (YES -- just broke sidebar w/ a recipe change by accident. Worth
automated testing of these components with empty state / bad data / good data)
-> Note: I've built a framework for testing the recipe widget simply enough
-> Testing save/edit buttons involves either having or mocking state and store
which is rather a pain...
TODO:
- Finish "Sharing" code (x)
-> Check if recipe is marked "shared" before showing it (x)
-> Implement "Share" button to make it shared (x)
-> Handle multiple recipes / collections (x)
- Fix import of frustrating NYT ingredients with multiple units...
- Copy recipe button...
- While we're at it... maybe clean up the API issue...
- Consider renaming the 400 things called "api" to something nicer. While you're at it, split code a bit
so files like remoteApi.js are less overwhelming.
- Import tweaks
- Fix Log-In and Auto-Sync process (?)
- Fix empty/startup state
- Create start/login page for chrome extension + app
- Test Syncing from local to cloud...
Maybe before publish?
- Simple export to file functionality (back-up) (part-way...)
- Allow pushing parsers from web-app to chrome extension so we don't have to update chrome extension (?)
- Create simple "sharing" interface -- "sharing" a recipe makes the
link public -- when people follow the link they get a recipe they
can copy to their DB (we strip the _ID and owner from it when
downloading...?)
=> Flag to be public or not
=> Links to public recipes work for anyone
=> You can add a recipe?
=> recipes as ingredients get added recursively
=> Copy recipe ability...
Quick Fix:
-> grams / second unit import (NYTimes!!!)
- Publish version 1
- Set-up dev branch in github and get a dev and a main URL working
- Fix sorting in firefox?
Wishlist / Next version
- Update routing so back buttons work to move you from e.g. recipe list to open recipe to shopping list
- Save "purchased" state of shopping list items
- Tweak layout on mobile.
Future
- i18n
- Look into FF extension/other browser extensions
- Consider moving more work to webworkers? e.g. recipe parsing?
- Set up DEV version + Stable version (???)
- Nutrition!