inventree/InvenTree
2
0
Fork 0
mirror of https://github.com/inventree/InvenTree.git synced 2025-06-23 07:10:55 +00:00
Code Activity

Fix common spelling mistakes (#4956)

Browse Source 
* add codespell

* first fixes

* doc fixes

* fix docstrings and comments

* functional changes

* docstrings again

* and docs again

* rename args

* add ignore

* use pre-commit for filtering instead

* ups

* fix typo in filter
This commit is contained in:
Matthias Mair
2023-06-03 16:04:52 +02:00
committed by GitHub
parent 5e2bfaa43a
commit 21ed4b2081
161 changed files with 344 additions and 334 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/docs/report/context_variables.md
View File

@ -89,8 +89,8 @@ Each part object has access to a lot of context variables about the part. The fo
| creation_date | Date that this part was added to the database
| creation_user | User who added this part to the database
| responsible | User who is responsible for this part (optional)
| starred | Wether the part is starred or not |
| disabled | Wether the part is disabled or not |
| starred | Whether the part is starred or not |
| disabled | Whether the part is disabled or not |
| total_stock | The total amount in stock |
| quantity_being_built | The amount being built |
| required_build_order_quantity | The amount required for build orders |
@ -98,7 +98,7 @@ Each part object has access to a lot of context variables about the part. The fo
| build_order_allocations | Query set with all build order allocations for that part |
| required_sales_order_quantity | The amount required for sales orders |
| allocated_sales_order_quantity | The amount allocated for sales orders |
| available | Wether the part is available or not |
| available | Whether the part is available or not |
| on_order | The amount that are on order |
| required | The total amount required for build orders and sales orders |
| allocated | The total amount allocated for build orders and sales orders |
@ -197,7 +197,7 @@ Each part object has access to a lot of context variables about the part. The fo
| pretty_name | The IPN, supplier name, supplier SKU and (if not null) manufacturer string joined by `|`. Ex. `P00037 | Company | 000021` |
| unit_pricing | The price for one unit. |
| price_breaks | Return the associated price breaks in the correct order |
| has_price_breaks | Wether this [SupplierPart](./context_variables.md#supplierpart) has price breaks |
| has_price_breaks | Whether this [SupplierPart](./context_variables.md#supplierpart) has price breaks |
| manufacturer_string | Format a MPN string for this [SupplierPart](./context_variables.md#supplierpart). Concatenates manufacture name and part number. |
### Manufacturers
@ -232,7 +232,7 @@ A [Sales Order](../order/sales_order.md) object has the following context variab
#### Return Order
A [Return Order](../order/return_order.md) object has the following context variables avaiable.
A [Return Order](../order/return_order.md) object has the following context variables available.
| Variable | Description |
| --- | --- |

2
docs/docs/report/labels.md
View File

@ -17,7 +17,7 @@ Label templates are written using a mixture of [HTML](https://www.w3schools.com/
A label template is a single `.html` file which is uploaded to the InvenTree server by the user.
Below is a reasonably simple example of a label template which demostrates much of the available functionality. The template code shown below will produce the following label:
Below is a reasonably simple example of a label template which demonstrates much of the available functionality. The template code shown below will produce the following label:
{% with id="label_example", url="report/label_example.png", description="Example label" %}
{% include 'img.html' %}

2
docs/docs/report/report.md
View File

@ -168,7 +168,7 @@ Report templates are created (and edited) via the [admin interface](../settings/
Only users with staff access can upload or edit report template files.
!!! info "Editing Reports"
Existing reports can be edited from the admin interface, in the same location as described above. To change the contents of the template, re-upload a template file, to overrie the existing template data.
Existing reports can be edited from the admin interface, in the same location as described above. To change the contents of the template, re-upload a template file, to override the existing template data.
### Name and Description