Skip to content

Model editor: add support for JSON data extensions - #4576

Draft
nickrolfe wants to merge 5 commits into
mainfrom
nickrolfe/model-editor-json
Draft

nickrolfe wants to merge 5 commits into
mainfrom
nickrolfe/model-editor-json

Conversation

@nickrolfe

@nickrolfe nickrolfe commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

This PR adds support to the model editor for loading JSON-formatted data extensions, in addition to the existing YAML format. When saving and overwriting existing extensions, it will preserve the file's existing format.

For now, new files will still be saved as YAML. We can change the definition of DEFAULT_EXTENSION_FORMAT_FOR_NEW_FILES to switch to JSON when we're ready.

I have done some manual testing:

  • creating a new model in the editor (in YAML), converting and renaming it to JSON, reloading the editor, modelling a new method, then saving and checking that the file gets saved as JSON.
  • I also checked that the CodeQL CLI was able to load that JSON file.

@nickrolfe nickrolfe added the Complexity: Medium Requires a moderate level of detail in design or review. label Oct 2, 2026
@nickrolfe
nickrolfe force-pushed the nickrolfe/model-editor-json branch from f1be112 to c2e2ac2 Compare October 2, 2026 16:09
This will allow us, for example, to switch to JSON as the default format
while keeping existing YAML files as YAML.

JSON (de)serialization is currently stubbed out, and will be implemented
in a follow-up commit.
@nickrolfe
nickrolfe force-pushed the nickrolfe/model-editor-json branch from c2e2ac2 to 8d067e1 Compare October 2, 2026 16:19

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Complexity: Medium Requires a moderate level of detail in design or review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant