Open privatemaker opened 1 year ago
Youβre right, I havenβt implemented comprehensive validation in Sveltia CMS. I think having a config editor is rather a must because hand-written config files are very problematic, but the CMS still needs a validator to catch any issue. In the meantime, please use Decap as a validator π€£
And yeah, I think your error is unrelated to search_fields
because the property is unused (not yet supported) in Sveltia CMS. Iβll figure out how it could happen.
Itβs a mystery at a glance. I thought it might be a browser compatibility issue because findLast
is relatively new, but it doesnβt make sense if it works with the local environment. π€
I think having a config editor is rather a must because hand-written config files are very problematic
Agreed ππ» that's the dream. One things i've wished for with Netlify/Decap (which diverges from a validation + editor) is that configs could be split into multiple files:
admin/
βββ index.html
βββ sveltia-cms.js
βββ config.yml
βββ collections/
βββ posts.yml
βββ pages.yml
βββ widgets.yml
This increases number of requests on load, but the collections could be lazy loaded so it's not too bad. This would progressively enhance, while being backwards compatible, yet allow a dev to wrangle the hundreds of lines of YAML a bit better.
I ran into another bug. After successfully doing the oauth dance, logging in, seeing request return
200
Sveltia UI updates and says
Loading Site Data...
but errors with following:When switching to
decap-cms / netlify-cms.js
I see the following error:After fixing a few bugs in my config and properly loading the content in Decap, I still see above error in Sveltia.
What is also interesting is the config works fine when using localhost version.