config.edn is not populated when creating a new DB graph, leading to configs set in there not applying

[lhewett946]

Search first

• I searched and no similar issues were found

What Happened?

It appears that config.edn needs to be populated with certain variables in order for Logseq to parse it correctly.

I noticed this issue because I was fiddling with some local changes I am working on that are configured using parameters in config.edn. I set up my new parameters in the empty file, but they were not being applied.

After copying and pasting the config.edn from an existing Markdown graph into the file, the settings I was configuring were now picked up.

Reproduce the Bug

1. Create a new DB graph from scratch (no imported data)
2. Open config.edn through the settings menu and observe that it is empty
3. (Optional): Add the graph forces section into the blank config.edn and notice that the values there are not applied when opening the graph view

Expected Behavior

Configuration options set up in config.edn should be applied without having to set other, unrelated, configuration options.

In the Markdown version (tested on demo.logseq.com @ logseq/logseq@29f7d5f) when creating a new graph the config.edn is pre-populated with various configuration options. Perhaps the DB version should be doing the same?

Files

No response

Browser, Desktop or Mobile Platform Information

test.logseq.com @ logseq/logseq@2193e3b

Chrome Version 135.0.7049.115 (Official Build) (64-bit)

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[logseq-cldwalker]

Hi. db graphs should have a config.edn. I've pushed a fix which should be up in ~10 min

[hdansou]

The config.edn is now generated.