@tiensonqin Thanks for the feedback. I think I've addressed 1 and 3. 5 requires some refactoring work so I've made an issue to do it later. I need some more detail on 2 and 4 so I'll ping u about em. I'll merge this soon unless there's more feedback today

@logseq-cldwalker Nice!
For 2, I mean to query pages/blocks by their names, e.g. logseq query graph-name "page-name".
For 4, to use Datascript's datoms for searching if there's no access token provided for search. Something like:

(->> (d/datoms db :aevt :block/title)
     (filter (fn [datom]
               (string/includes? (:v datom) search-input))))

Another idea is to add an append command to write some text to the db with the http api. e.g. logseq append graph-name "some text".

For 2, I mean to query pages/blocks by their names, e.g. logseq query graph-name "page-name".
For 4, to use Datascript's datoms for searching if there's no access token provided for search. Something like:

Addressed these in cc1093a. For 2, I added it as an option e.g. logseq query graph-name "page-name" -t because a string is already used to invoke a datalog query or a uuid string local entity query. Fwiw for predefined queries like this, it'd eventually be worth having a separate command as it allows for more powerful and custom queries by the user as I explored in https://github.com/cldwalker/logseq-query. logseq query is focused on invoking simple or advanced/datalog queries

Going to do an initial release of the CLI soon

Another idea is to add an append command to write some text to the db with the http api. e.g. logseq append graph-name "some text"

Good idea. Have questions so made this an issue - https://test.logseq.com/#/page/689ca670-d93f-4fe0-a262-029d95f8450f

Thanks for supporting 2 and 4 so quickly! 👍
And looking forward to the CLI release!