Document selecting API error language - #115
Closed
javorosas wants to merge 1 commit into
Closed
Conversation
Member
Author
|
Closing this PR because the SDK already supports custom request headers. The Accept-Language usage will be documented centrally in facturapi-docs. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documents how to request English API V2 errors using the SDK's existing
headersconstructor option, available since 4.17.0. The example covers regional variants, fallback behavior, stable codes, external messages, local SDK errors, and instance-level configuration.The existing Node and browser custom-header tests now explicitly verify that
Accept-Language: en-USreaches the request alongside SDK authentication.Validation: full
pnpm testpassed, including build, 34 runtime tests, and type tests; lint passed.