aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2023-01-07 17:36:44 +0100
committerJay Berkenbilt <ejb@ql.org>2023-01-07 21:25:05 +0100
commit98dff4631019faa3d72ac53c18e545f5fd9e131a (patch)
treee0b6796197eed7bfad001081443058417d85cd49
parent60538f1958e5ef59a9c39a95f15fa62cf5cda8ce (diff)
downloadqpdf-98dff4631019faa3d72ac53c18e545f5fd9e131a.tar.zst
TODO updates
-rw-r--r--TODO15
1 files changed, 14 insertions, 1 deletions
diff --git a/TODO b/TODO
index fbd8a9bf..2e42edba 100644
--- a/TODO
+++ b/TODO
@@ -9,7 +9,20 @@ Always
Next
====
-* Break ground on "Document-level work"
+* std::string_view transition -- work being done by m-holger
+* Break ground on "Document-level work" -- TODO-pages.md lives on a
+ separate branch.
+* Standard for CLI and Job JSON support for JSON-based command-line
+ arguments. Come up with a standard way of supporting command-line
+ arguments that take JSON specifications of things so that
+ * there is a predictable way to indicate whether an argument is a
+ file or a JSON blob
+ * with QPDFJob JSON, make sure it is possible to directly include
+ the JSON rather than having to stringify a JSON blob
+ * One option might be to prepend file:// to a filename or otherwise
+ to take a JSON blob. We could have that as a particular type of
+ argument that would behave properly for both job JSON and CLI.
+
Possible future JSON enhancements
=================================