Erez Rokah

Closing as stale, we can re-open if needed

Hi @ei-grad 👋 We would love to explore this further, do you have some initial benchmarks you can share on the benefits from the change?

Fixing this might be just about reading the initial value from the config here: https://github.com/netlify/netlify-cms/blob/9f219d395803075d9fe363c5366fb9bbf6fe38ae/packages/netlify-cms-core/src/backend.ts#L274 (and verifying it works for the all the different backends)

As discussed internally this is not a bug with the JSONFlattener, but rather with the Azure plugin, and should be fixed in the JSON schema generation for that plugin ([link...

Thanks @evelew, a possible place to start is here https://github.com/netlify/netlify-cms/blob/6d801ae092a6763bd751cb82bd238c7c12b31884/packages/netlify-cms-widget-object/src/ObjectControl.js#L66 Also see our contribution guide https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md

Going to close this as stale, at least until we get reports on performance issues with DuckDB. Please re-open if you think we still need this with benchmarks of how...

Thanks @agairing, looks like origin contains the schema and port too: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage#The_dispatched_event We would gladly accept a PR for it (probably we just need to parse `base_url` and reconstruct without...

How about `e.origin !== new URL(this.base_url).origin` ? It makes it clear what we're checking and is stricter.

@agairing, thanks for letting us know. I opened an new issue for that https://github.com/netlify/netlify-cms/issues/3655 and I'm surprised our CI doesn't fail it since it we run the tests on Widows...

Thanks @Chathula for opening this.