accounting/books
2
0
Fork 0
mirror of https://github.com/frappe/books.git synced 2024-11-09 23:30:56 +00:00
Code Issues Releases Activity
2bffcda8ff
books/schemas
History
Mildred Ki'Lya 2bffcda8ff feat: #755 Accounting for taxes on payments 
When defining taxes, it is possible to define an additional payment
account that will be used during payments to move taxes from the
original tax account to this new payment tax account. This allows to
account for taxes only when payment is received.

Now payments can reference tax summary objects that will reference the
two accounts to move funds between when the payment is committed. Reuse
some of the Invoice code to generate these tax summary objects.
2023-12-22 10:07:47 +01:00
..
app feat: #755 Accounting for taxes on payments 2023-12-22 10:07:47 +01:00
core fix: isRequired handling 2023-09-20 23:33:48 -07:00
meta incr: add collapsible sections 2023-02-17 21:56:54 +05:30
regional Add regional schemas for Switzerland. 2023-11-28 22:14:35 +01:00
tests chore: format files using prettier 2023-06-27 13:11:15 +05:30
index.ts fix: isRequired handling 2023-09-20 23:33:48 -07:00
README.md chore: format files using prettier 2023-06-27 13:11:15 +05:30
schemas.ts feat: pos settings 2023-12-04 14:38:13 +05:30
types.ts incr: add customization schemas and models 2023-07-31 12:38:32 +05:30

README.md

Schema

Main purpose of this is to describe the shape of the models' table in the database. But there is some irrelevant information in the schemas with respect to this goal. This is information is allowed as long as it is not dynamic, which is impossible anyways as the files are data (.json, not .js)

If any field has to have a dynamic value, it should be added to the controller file by the same name, check the books/models subdirectory for this.

There are a few types of schemas:

  • Regional: Schemas that are in the '../regional' subdirectories these can be of any of the below types.
  • Abstract: Schemas that are not used as they are but only after they are extended by Stub schemas. Indentified by the isAbstract field
  • Subclass: Schemas that have an "extends" field on them, the value of which points to an Abstract schema.
  • Complete: Schemas which are neither abstract nor stub.

For more detail on the meta structure of the schema check books/schemas/types.ts.

Final Schema

This is the schema which is used by the database and app code and is built by combining the above types of schemas.

The order in which a schema is built is:

  1. Build Regional schemas by overriding the fields and other properties of the non regional variants.
  2. Combine Subclass schemas with Abstract schemas to get complete schemas.

Note: if a Regional schema is not present as a non regional variant it's used as it is.

Additional Notes

In all the schemas, the "name" field/column is the primary key. If it isn't explicitly added, the schema builder will add it in.

The following schema fields will be implicitly translated by the frontend: "label", "description", and "placeholder", irrespective of nesting.