Skip to content

Conversation

@vitaminmoo
Copy link
Contributor

@vitaminmoo vitaminmoo commented Dec 22, 2025

  • Aiming for consistency between poe2/ and the top level files
  • Also aiming to enable programmatic manipulation
  • Automatically done by a tool, trivial to redo if stuff changes
  • Comments preserved
  • I have verified that it has no impact on the resulting schemas (see
    #196)
  • Version comments added for all definitions currently inside files with versions in the name, so I believe no information is lost
  • It fixed one difference in poe2 file name vs definition name
  • It added some trailing carriage returns but that seems sane?

I'm happy to upload the tool I used to make this if that is preferred over this mega-pr.

- Aiming for consistency between poe2/ and the top level files
- Also aiming to enable programmatic manipulation
- Automatically done by a tool, trivial to redo if stuff changes
- Comments preserved
- I have verified that it has no impact on the resulting schemas (see
  [poe-tool-dev#196](poe-tool-dev#196))
- Version comments added for all definitions currently inside files with versions in the name, so I believe no information is lost
- It fixed one difference in poe2 file name vs definition name
- It added some trailing carriage returns but that seems sane?
@SnosMe
Copy link
Collaborator

SnosMe commented Dec 22, 2025

Rejecting, you can experiment manipulation on poe2 first .

@vitaminmoo vitaminmoo closed this Dec 22, 2025
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