mirror of
https://github.com/inventree/InvenTree.git
synced 2025-06-14 11:05:41 +00:00
chore(backend): bump devtools (#9088)
* chore(backend):Bump devtools * fix typos that are now detected
This commit is contained in:
@ -6,7 +6,7 @@ title: Part Templates
|
||||
|
||||
There are various purposes for using Part Templates, among them:
|
||||
|
||||
* Template parts can hold information that can be re-used across "Variants", a template part could be useful for creating a base variant of an assembly which can be derived from, with BoM changes for instance.
|
||||
* Template parts can hold information that can be reused across "Variants", a template part could be useful for creating a base variant of an assembly which can be derived from, with BoM changes for instance.
|
||||
* Variants can be used as "manufacturing variants" where the variant dictates a particular configuration which a customer can order: a variant might determine the particular options that come with a part, like harnesses, enclosure, color, specs, etc.
|
||||
|
||||
"Variants" parts will reference the "Template" part therefore explicitly creating and showing direct relationship.
|
||||
|
@ -182,7 +182,7 @@ Asset files can be rendered directly into the template as follows
|
||||
|
||||
## Report Snippets
|
||||
|
||||
A powerful feature provided by the django / WeasyPrint templating framework is the ability to include external template files. This allows commonly used template features to be broken out into separate files and re-used across multiple templates.
|
||||
A powerful feature provided by the django / WeasyPrint templating framework is the ability to include external template files. This allows commonly used template features to be broken out into separate files and reused across multiple templates.
|
||||
|
||||
To support this, InvenTree provides report "snippets" - short (or not so short) template files which cannot be rendered by themselves, but can be called from other templates.
|
||||
|
||||
|
Reference in New Issue
Block a user