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.

Sign up for GitHub

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

Jump to bottom

TUTORIAL: Describe standard invoice fields #519

Merged
merged 1 commit into from
Aug 9, 2023
Merged

TUTORIAL: Describe standard invoice fields #519

merged 1 commit into from
Aug 9, 2023

Conversation

rmilecki
Copy link
Collaborator

@rmilecki rmilecki commented Aug 6, 2023 

By default there are 3 required fields: date, invoice_number and amount.
As a result those 3 names became de facto a 3 standarized names so far.
Describe them to prepare for introducing more standard names *LATER*.

TUTORIAL: Describe standard invoice fields
26bb5a0 
By default there are 3 required fields: date, invoice_number and amount.
As a result those 3 names became de facto a 3 standardized names so far.
Describe them to prepare for introducing more standard names *LATER*.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
@rmilecki rmilecki force-pushed the tutorial-describe-fields branch from 9bc486a to 26bb5a0 Compare August 6, 2023 11:58
@rmilecki
Copy link
Collaborator Author

rmilecki commented Aug 6, 2023

In this pull request I would like to describe 3 already standardized fields. Just that. Nothing more.

Please let me know if my description of those 3 fields is OK.

More standard names can be introduced later. That is out of the scope of this pull request. Let's discuss that in different pull requests please.

@rmilecki rmilecki merged commit 6d8eec3 into invoice-x:master Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bosd bosd bosd approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rmilecki @bosd