Skip to content

Conversation

vincent-pochet
Copy link
Collaborator

@vincent-pochet vincent-pochet commented Aug 28, 2025

Context

This PR is a new approach to #4211

The goal here is to make sure that we will not accidentally persist a Invoice that was not supposed to be.

Description

Instead of relying on a Invoice model, it introduces a new FakeInvoice defined as a Data structure

@vincent-pochet vincent-pochet marked this pull request as ready for review August 28, 2025 09:04
Copy link
Contributor

@groyoh groyoh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would freeze on the invoice work instead or do we expect to modify some attributes ?

@vincent-pochet
Copy link
Collaborator Author

Would freeze on the invoice work instead or do we expect to modify some attributes ?

It could work, we are not not modifying anything. Still I prefer to use a dedicated structure, it could save some unexpected behavior.

@vincent-pochet vincent-pochet merged commit 66b3f41 into main Aug 28, 2025
21 of 22 checks passed
@vincent-pochet vincent-pochet deleted the misc-fake-invoice branch August 28, 2025 09:22
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.

2 participants