roam-traverse-graph-settings

words:	198 + 880 = 1078
last update:

```javascript module.exports = () => { return { version: 1, publicGlobalTags: [ "#public" ], publicTags: [ "public", "codemods", "roam-traverse-graph", "git-rebase", "git-stacked-rebase", 'software i hate', "typescript", ], publicOnlyTags: [ "po", "tp" ], privateTags: [ "private", "ppl", "pipedrive", ], } } ```
```javascript module.exports = () => { return { version: 0, publicGlobalTags: [ "#public" ], publicTags: [ "#public", "#codemods", "[[codemods]]", "#roam-traverse-graph", "[[roam-traverse-graph]]", "#git-rebase", "[[git-rebase]]", "#git-stacked-rebase", "[[git-stacked-rebase]]", '#[[software i hate]]', '[[software i hate]]', "#typescript", "[[typescript]]", ], publicOnlyTags: [ "#po", "#tp" ], privateTags: [ "#private", "[[private]]", "#[[private]]", "private::", "#ppl", "[[ppl]]", "#pipedrive", "[[pipedrive]]" ], } } ```
#public
{{[[DONE]]}} ~~new~~
- meh! updating would require parsing the javascript AST, instead of just creating a new block in roam
  - ```javascript module.exports = () => { return { "1": { publicGlobalTags: [ "#public" ], publicTags: [ "public", "codemods", "roam-traverse-graph", "git-rebase", "git-stacked-rebase", "software i hate (public)", ], publicOnlyTags: [ "po", "tp" ], privateTags: [ "private", "ppl", "pipedrive", ], }, "0": { publicGlobalTags: [ "#public" ], publicTags: [ "#public", "#codemods", "[[codemods]]", "#roam-traverse-graph", "[[roam-traverse-graph]]", "#git-rebase", "[[git-rebase]]", "#git-stacked-rebase", "[[git-stacked-rebase]]", "[[software i hate (public)]]", "#typescript", "[[typescript]]", ], publicOnlyTags: [ "#po", "#tp" ], privateTags: [ "#private", "[[private]]", "#[[private]]", "private::", "#ppl", "[[ppl]]", "#pipedrive", "[[pipedrive]]" ], } } } ```
cc:
- (should have no effect for [[roam-traverse-graph]])
- [[public]]
- todo: private!
- [[(hidden) l6bezRkPb]]
- [[(hidden) hMBgHmSNk]]

Linked Mentions (23 in 21 pages)

November 2nd, 2021 (1)

{{[[TODO]]}} implements settings thru roam itself 👀[[roam-traverse-graph-settings]]

(hidden) hMBgHmSNk (1)

(hidden) d5Oy41JMT [[roam-traverse-graph-settings]]

November 14th, 2021 (1)

{{[[TODO]]}} read config from [[roam-traverse-graph-settings]]

November 17th, 2021 (1)

e.g. exposing a wrapper fn `allowAnyTextMatch` from the `ctx` param in the settings creator fn in [[roam-traverse-graph-settings]] that could wrap a string & thus have a work-around.

November 27th, 2021 (1)

{{[[TODO]]}} split [[roam-traverse-graph-settings]] into per-plugin basis

git-rebase (1)

[[roam-traverse-graph-settings]]

November 29th, 2021 (2)

more benefit for the page itself because it sees itself mentioned in the #[[(hidden) tm2-dKJbJ]], instead of manually checking the [[roam-traverse-graph-settings]] page.
{{[[TODO]]}} instead of having the `publicTags` in [[roam-traverse-graph-settings]], we probably should have a conventional tag like #[[(hidden) tm2-dKJbJ]] which one could use to mark pages as `publicTag`s.
- similar to how I __thought__ I used the `#public` (global) tag lol
  - {{[[TODO]]}} complexity is hard man, we need (integration) tests big time
- better because inside the #[[(hidden) tm2-dKJbJ]] page, you see what pages will make your stuff public
  - more benefit for the page itself because it sees itself mentioned in the #[[(hidden) tm2-dKJbJ]], instead of manually checking the [[roam-traverse-graph-settings]] page.
  - tho idk, not sure yet, maybe we need a better name than #[[(hidden) tm2-dKJbJ]], to make it clear. if it is very understandable, then sure

roam (1)

[[roam-traverse-graph-settings]]

(hidden) S-ygYfi0j (1)

(hidden) iVMvWJg7l [[roam-traverse-graph-settings]]

corporate overlords (1)

{{[[TODO]]}} TODO #[[(hidden) _I12W6mwv]], cc [[roam-traverse-graph-settings]]

newest-first (1)

[[roam-traverse-graph-settings]]
- {{[[TODO]]}} make configurable

oldest-first (1)

[[roam-traverse-graph-settings]]
- {{[[TODO]]}} make configurable

bus factor (tbd) (1)

[[roam-traverse-graph-settings]]

software i hate (1)

[[roam-traverse-graph-settings]]

December 23rd, 2021 (2)

{{[[TODO]]}} but, for this to work smoothly, we kinda would need to double down on the "having most things in [[roam-traverse-graph-settings]]" that we want configured, instead of configuring things there such as "tag-that-makes-other-pages-public-recursive", whom would in turn be used in pages directly - this would mean it's easier for the [[roam]] user to use (probably? + info via linked references), but harder for tools to parse, because instead of parsing just the 1 single settings page, you have to parse it, and then parse all the related pages as well.
- ofc, maybe [[roam]] in the future could provide APIs that would help work around this (e.g. user gets best xp w/ 2nd option; tools can use API to quickly find all pages that have the tag mentioned)
  - {{[[TODO]]}} wait but now that i say it this way, isn't it __exactly__ what `roamAlphaAPI.query` is like? 🤯
(hidden) rL84VgAnU [[roam-traverse-graph-settings]]
- [[roam-traverse-graph]] [[export-html-pages]]
  - {{[[TODO]]}} new #[[(hidden) jOMmlCP4S]] - public recursive tag, but only if the page that is made public recursive, is mentioned in root level of a page (1st lvl child block) & has nothing else inside it (just like i often do in daily notes when referencing other pages & "writing into them" via linked references).
    - though, hmm, sometimes we still want it even if it's not on the root lvl of the page. e.g. just like right here.
      - then, maybe it's fine if it can be on any level, as long as it's the only one mentioned there
        
        though, in this case, still wouldn't apply. perhaps if both (all) linked references mentioned there are public, and no private ones (or private-making ones?), only then could give an exception.
        
        though, also gotta think if it's worth "complicating" so much the logic that it's no longer worth
  - {{[[TODO]]}} oh snap, inspired straight from the [previous one](((HW3tg57Ww))) - having a `roam/js` or whatever "extension" to add the simplest of indicators if something will be public -- would be great!
    - {{[[TODO]]}} maybe on hover, could even explain why
    - {{[[TODO]]}} but, for this to work smoothly, we kinda would need to double down on the "having most things in [[roam-traverse-graph-settings]]" that we want configured, instead of configuring things there such as "tag-that-makes-other-pages-public-recursive", whom would in turn be used in pages directly - this would mean it's easier for the [[roam]] user to use (probably? + info via linked references), but harder for tools to parse, because instead of parsing just the 1 single settings page, you have to parse it, and then parse all the related pages as well.
      - ofc, maybe [[roam]] in the future could provide APIs that would help work around this (e.g. user gets best xp w/ 2nd option; tools can use API to quickly find all pages that have the tag mentioned)
        
        {{[[TODO]]}} wait but now that i say it this way, isn't it __exactly__ what `roamAlphaAPI.query` is like? 🤯
  - {{[[TODO]]}} another one re: the total global word count as a number in the landing page
    - we could have it be a button (well, a tag with href) that navigates to a page that has a graph (chart) of (top secret what it shows)
      - {{[[TODO]]}} oo even more ideas - something like [[(hidden) btHMgS_i0]] has w/ "cool" statistics (normies represent, am i right?)
        
        {{[[TODO]]}} #[[(hidden) D1lY0CG5e]] [[roam]] lmao just noticed - let me scroll to the very bottom of the page, even though there's no content there (i.e. like vim) - would be useful when i have some block opened & editing & want to scroll the current text higher into the view w/o creating a bunch of empty blocks below it.
- (hidden) etq9XMnlS

roam-traverse-graph (1)

configured in [[roam-traverse-graph-settings]]

January 6th, 2022 (1)

{{[[TODO]]}} would need to have a predefined base url for the notes in the [[roam-traverse-graph-settings]] page.
- observation:: hmm, a reason why you wouldn't want to have meta-tags (e.g. tags that make other tags have [[magic]])

typescript (1)

#roam-traverse-graph-settings

February 3rd, 2022 (1)

{{[[TODO]]}} gotta implement `latest-supported-settings-version` now, before can continue w/ AST parsing -- need different settings version for the first time for #roam-traverse-graph-settings

meta (1)

[[roam-traverse-graph-settings]]

react libs (1)

[[roam-traverse-graph-settings]]