Skip to content
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

Add schema pain.001.003.03 #31

Closed
wants to merge 1 commit into from
Closed

Conversation

tloebhard
Copy link

Added pain.001.003.03.xsd as a copy of pain.001.001.03.xsd (with adjusted namespace). Fixes #20

Added sepaxml/schemas/pain.001.003.03.xsd as a copy of sepaxml/schemas/pain.001.001.03.xsd (with adjusted namespace). Fixes raphaelm#20
@codecov
Copy link

codecov bot commented Jan 15, 2021

Codecov Report

Merging #31 (db2331f) into master (696d45b) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   97.01%   97.01%           
=======================================
  Files          23       23           
  Lines         906      906           
=======================================
  Hits          879      879           
  Misses         27       27           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 696d45b...db2331f. Read the comment docs.

@MoritzFago
Copy link

What's the status on this? This missing currently breaks sepa transfers for byro-fints.

@tloebhard
Copy link
Author

@MoritzFago does my pull request (adding just the file...) also fix your issue?

@raphaelm
Copy link
Owner

raphaelm commented Dec 5, 2021

Sorry for not merging this, just copying the file and renaming it doesn't feel right, we should actually use the correct schema. See df5eb8d

@raphaelm raphaelm closed this Dec 5, 2021
@tloebhard
Copy link
Author

Sorry for not merging this, just copying the file and renaming it doesn't feel right, we should actually use the correct schema. See df5eb8d

Indeed, that was no famous solution - just pragmatic, as explained in #20 .

Thank you for solving!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support more SEPA versions?
3 participants