-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
billing sample data #17
Conversation
…nged one name to include special characters
…earing office with authority to collect
…ptional; more precise dates in sample data
… therefore stopping to create a ESK segment for each Leistung with a different Vergütungsart
…nth and one MAN segment per INV
# Conflicts: # package.json # tsconfig.json
…s some fixes for minor mistakes found by validation
Also includes payload data validation according to #18, but only for SGB XI yet. |
Thank you for reviewing! Do you approve the PR with my changes and answers? |
Maybe one thing, I figure that could be done later. You have some utility functions like |
I see your point. Okay, let's call it mapEachKostentraeger. I know the name was misleading and I chose it to align the lines 54 – 64 with the documentation on pages 12 - 14, but I think mapEach… is better now. |
No description provided.