I have a dev related question. Could we perhaps remove the appearance related configs from the workspaces? Since most users of VSCode have these settings inside their User config and the Workspace config overrides the userconfig.

Yeah, I can't use anything brighter than an amber theme now 😄 I agree with this suggestion.

I got my self the Dracula Pro theme and well its always fun to open something and having something else shown making me Look where the setting was set.

I have a funny problem I'm on windows with wsl and I can't run the init script:

Problem found git checked everything out as crlf and well wsl wants only lf reason for using wsl since their are only sh script files to bootstrap it

are there any appearance related configs left? just removed github light from the bundle with the last release so that should be the last of appearance related configs

I didn't mean the release I meant the dendron.code-workspace in the repo xD

lol, got it. yeah, completely. @User was going to do that but then went to hawaii 😛 feel free to submit a PR, otherwise, i'll update it for this weeks' early seed release

pr is open https://github.com/dendronhq/dendron/pull/423

merged!

And for the graph view I will probably start with the web view and Integrate filters and options to style it. The next step after that would be to save filters and the styles. And after that I would look at what needs to be changed or adjusted for the Links.

sounds good. i've written up setup instructions here: https://dendron.so/notes/9af9cf56-d2a0-47d1-b8bf-5a02c42ac2fd.html here are the two open issues we have for graph features: - https://github.com/dendronhq/dendron/issues/387 - https://github.com/dendronhq/dendron/issues/307

heads up that the dendron.so website is now being published using 11ty 🙂 let me know if anyone notices anything out of place - it should function the same as the old site in all respects except the syntax highlighting - we're using https://prismjs.com/ to do syntax highlighting so colors might be... bolder... than what you were used to 😅 i also still need to add the "edit on github link" back to the footer https://dendron.so/ @User @User @User @User

One question I still have is should the Root node still be Linked to. I mean yes if I define a schema it needs to have Root as a Parent. > Question is Why, a flag like Domain: true Or Type: Domain Should work as well. If it get's not linked It would make it easier in the Graph view to separate the domains and only Highlight where they connect through links/tags

wouldn’t be a bad idea. i’m open to it 🙂

@User just pushed an update to the dendron-cli. if you run the following in your workspace, you should be able to build now

npm install @dendronhq/dendron-cli@latest
npm install @dendronhq/dendron-11ty@latest

@User fyi, i've switched the dendron site to build off github actions instead. have modified the workflow you posted here (https://dendron.so/notes/692fa114-f798-467f-a0b9-3cccc327aa6f.html#publish-to-github-pages-with-actions) and writing up instructions on how to do this for the 11ty based website 🙂

@User question which branch should I use? they are a bit confusing

and second thing when i try to run the extension I get the following

11ty built for both dendron-site and ocwphy but the sites end up with big svg buttons. Not sure why. I attached the output.

@User do you have anything against us introducing something like https://github.com/tribou/jest-serializer-path to get rid of the absolute paths in Jest snapshots so we can drop

-s

?

That aside the tests look pretty good now: https://github.com/LukeCarrier/dendron/actions/runs/442563495

master branch has the latest stble code

can you dm me the contents of the detailed log when you run webpack?

Will do when I'm back at my pc

And in response to your message in #735365126227493004 i would still need to implement the filtering code since I think it would be good to have the graph view as a custom element with the filtering to make it useable for publishing. So that the graph view can be reused and doesn't need to be reimplemented

nope, think that's a great idea. you can use

lerna add -D

to add it to all packages

woot! all i want for christmas this year is a working ci/cd 🙂

All I want this year is Windows to not be a pain in the rear... every time haha

I think we'd do well to replace use of Bash scripts with Node, if just to make getting set up on Windows require one less dependency. I'm always wary of MSYS and Cygwin because of how much other stuff tends to break when you introduce them