Skip to content

Improved Schema Input Format for PD#395

Draft
lukelowry wants to merge 1 commit intodevelopfrom
lukel/input-format-dev
Draft

Improved Schema Input Format for PD#395
lukelowry wants to merge 1 commit intodevelopfrom
lukel/input-format-dev

Conversation

@lukelowry
Copy link
Copy Markdown
Collaborator

Description

More consistant and navigatable schema which will make case translation much easier for both ingress and egress

Proposed changes

  • branches are promoted to same level as buses to support many branch types

Checklist

Documentation only

Further comments

TBD

@lukelowry lukelowry requested review from PhilipFackler and pelesh May 6, 2026 21:28
Copy link
Copy Markdown
Collaborator

@PhilipFackler PhilipFackler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a judgement about this, so I'll let someone else approve. It would be nice to see an example json file to get a better idea of what this changes and what will need to change in the parser functions.

...I guess this PR should ideally end up including changes to the parser functions and the all the existing input files.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants