-
Notifications
You must be signed in to change notification settings - Fork 8
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
Veri*Factu Addon #410
Veri*Factu Addon #410
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #410 +/- ##
==========================================
+ Coverage 81.64% 82.21% +0.56%
==========================================
Files 235 238 +3
Lines 11546 11751 +205
==========================================
+ Hits 9427 9661 +234
+ Misses 1756 1727 -29
Partials 363 363 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! I think it makes sense to only cover the most basic cases, and to leave things like reverse charges to the user, as using scenarios was risky.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔝 🎩
Describe your changes
Add-on for the Ver*Factu Regulation. Includes:
es-verifactu-doc-type
for document type andes-verifactu-tax-classification
to cover tax exemptions and overall classification. They correspond to L2 and L9/10 from the BOE order, at the very bottom.es-verifactu-doc-type
extension.es-verifactu-tax-classification
extension.general
that, like with TicketBAI, acts as the invoice description.es-verifactu-doc-type
extension based on invoice information.Factura emitida en sustitución de facturas simplificadas facturadas y declaradas.
, to cover the case when a client that has received a simplified invoice then asks for a full one.Checklist before requesting a review
I have added thorough tests with at least 90% code coverage.Coverage tops out at 87% because of invoice nil checks. Could add tests although they would be somewhat redundant.go generate .
to ensure that Schemas and Regime data are up to date.