aboutsummaryrefslogtreecommitdiffstats
path: root/rust/TODO
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2018-09-11 13:56:53 -0700
committerBryan Newbold <bnewbold@robocracy.org>2018-09-11 13:56:53 -0700
commit0dc872921023030f6ffd320eb038e5379b47fa53 (patch)
tree7069b0a3c914431d4e0e7f05d2526592b0c4e3cf /rust/TODO
parent98f21fe69e0361db00e5fbceb7a3168dcb926d32 (diff)
downloadfatcat-0dc872921023030f6ffd320eb038e5379b47fa53.tar.gz
fatcat-0dc872921023030f6ffd320eb038e5379b47fa53.zip
update TODO lists (september plan)
Diffstat (limited to 'rust/TODO')
-rw-r--r--rust/TODO47
1 files changed, 31 insertions, 16 deletions
diff --git a/rust/TODO b/rust/TODO
index ac378961..c922d5df 100644
--- a/rust/TODO
+++ b/rust/TODO
@@ -1,24 +1,40 @@
-verbs:
+refactors
+- fatcatd -> fatcat-api-server
+- fatcat_api -> fatcat_api_schema (or spec? models? types?)
+- standardize "mutating"/"edit" actions
+ => have editgroup_id be a request-level param everywhere (not entity-level;
+ for batch)
+ => editgroup_id as query param
+ => editor_id from auth (header)
+- consistent "expand"/"stub" flags
+
+correctness
- enforce "previous_rev" required in updates
+- reread/review editgroup accept code
+- enforce "no editing if editgroup accepted" behavior
+- changelog sequence without gaps
+- batch insert editgroup behavior; always a new editgroup?
+
+edit lifecycle
+- editgroup: state to track review status?
+- per-edit extra JSON
+
+account helper tool
+- set admin bit
+- create editors
+- create keypairs
+- generate tokens
+- test/validate tokens
-- review editgroup accept code (?)
-- fatcat_api -> fatcat_api_schema (or spec? models? types?)
-- generally, standardize "edit" actions
-- fatcat -> fatcat-api-server
-- editgroup param to update
- => also for creation? for consistency
-- editor_id vs. editor username; return editor_id (in addition to name?)
later:
-- have editgroup_id be a request-level param everywhere (not entity-level; for batch)
-- editgroup: state to track review status?
-- re-implement old python tests
-- enforce "no editing if editgroup accepted" behavior
-- real auth
-- metrics, jwt, config, sentry
-- ansible/deployment/DNS story
+- pure-rust "benchmark" scripts that hit, eg, lookups and batch endpoints
+ => criterion.rs benchmarking
+- try new actix/openapi3 codegen branch
- refactor logging; use slog
+- test using hash indexes for some UUID column indexes, or at least sha1 and
+ other hashes (abstracts, file lookups)
schema/api questions:
- url table (for files)
@@ -26,4 +42,3 @@ schema/api questions:
- "types"
- define release field stuff
- what should entity POST return? include both the entity and the edit?
-