Expose ErrorReason enum in exports #245
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
miparnisari
approved these changes
Oct 6, 2025
tstirrat15
force-pushed
the
expose-error-reason
branch
from
afac31b to
359f841
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This was raised by a discord user: https://discord.com/channels/844600078504951838/844600078948630559/1424792180207128588
Everything in this library that needs to be exposed needs to be explicitly exported. The
ErrorReasonenum wasn't one of those things. This fixes that.Changes
ErrorReasonenumTesting
Review. See that tests pass. See that you can then import the
ErrorReasonenum and compare against it.