fix: correct XSD element ordering for allowances and charges#107
Merged
jslno merged 1 commit intojslno:mainfrom Dec 11, 2025
Merged
fix: correct XSD element ordering for allowances and charges#107jslno merged 1 commit intojslno:mainfrom
jslno merged 1 commit intojslno:mainfrom
Conversation
Contributor
|
@smnbbrv is attempting to deploy a commit to the better-auth-extended Team on Vercel. A member of the Team first needs to authorize it. |
commit: |
Contributor
Author
|
@jslno hope it goes well. I'm happy to have a feedback |
jslno
approved these changes
Dec 11, 2025
Owner
jslno
left a comment
There was a problem hiding this comment.
LGTM. Im currently quite busy, so not sure when I'll find time to publish
Contributor
Author
|
@jslno thanks! I have hardcoded it ATM in the project, so no hurry |
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
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.
Hi and thank you for your work on this project!
I have faced an issue today that the extended profile generates the TypeCode after other parameters in the allowances and charges and fails XSD validation. See below
Minimal repro:
The fix I found works well, not sure however how does it fit into the whole project architecture and idea.