Skip to content

Expose validation response types #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 30, 2025
Merged

Expose validation response types #151

merged 1 commit into from
Aug 30, 2025

Conversation

ItsHarper
Copy link
Contributor

These types are useful for writing convenience functions and the like. They are already part of the public API indirectly, so the only flexibility lost by exposing them is the ability to rename or condense them.

@ItsHarper
Copy link
Contributor Author

ItsHarper commented Aug 30, 2025 •
edited
Loading

The XOptions interfaces should also be exposed, but I think first the message field should be removed, since I believe it's excluded everywhere it's used. Should I file an issue for all of that?

@ItsHarper ItsHarper changed the title Expose validation response types Expose useful types that are currently only available internally Aug 30, 2025
@ItsHarper ItsHarper changed the title Expose useful types that are currently only available internally Expose validation response types Aug 30, 2025
@fraxken fraxken merged commit 064018f into TopCli:main Aug 30, 2025
9 checks passed
@ItsHarper ItsHarper deleted the feat/expose-validation-types branch August 31, 2025 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fraxken fraxken fraxken approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ItsHarper @fraxken