Skip to content

Conversation

@jdesrosiers
Copy link
Collaborator

After fixing some type errors in @hyperjump/json-schema, it exposed a type issue in the plugin system. We aren't using the plugin system, so I decided to just remove it for now instead of fix it. Something like it can be added in again later if it turns out we need it. Not sure why we added in the first place.

After fixing some type errors in @hyperjump/json-schema, it exposed a
type issue in the plugin system. We aren't using the plugin system, so I
decided to just remove it for now instead of fix it. Something like it
can be added in again later if it turns out we need it.
@jdesrosiers
Copy link
Collaborator Author

Usually I wouldn't do this, but I'm going to merge this with automation failing because the failing test is going to be fixed separately in #90. If I wait for that PR before fixing this, then that PR will have the automation failures this PR is fixing. Either way, one of these PRs will need to be merged in a failing state.

@jdesrosiers jdesrosiers merged commit ef318a0 into main Nov 25, 2025
0 of 2 checks passed
@jdesrosiers jdesrosiers deleted the remove-plugins branch November 27, 2025 05:15
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