mirror of
https://github.com/inventree/InvenTree.git
synced 2025-11-14 11:56:44 +00:00
Docs refactor (#9545)
* Refactor / reognaize docs structure * Refactor plugin docs structure * More refactoring / cleanup * Update build images * Gallery updates * Order images * Update part docs * Settings images * Stock images * Reitntroduce gallery * Add custom icon macro * Update icons * Cleanup * Fix link * Fix internal links * Revert some page moves * Fix links * Fix links
This commit is contained in:
@@ -4,7 +4,7 @@ title: Interactive API
|
||||
|
||||
## Interactive API
|
||||
|
||||
If the server is running in [Debug Mode](../start/intro.md#debug-mode) then an interactive version of the API is available using a browser.
|
||||
If the server is running in [Debug Mode](../start/index.md#debug-mode) then an interactive version of the API is available using a browser.
|
||||
|
||||
!!! info "Debug Mode"
|
||||
This interactive API is only available when running the server in debug mode
|
||||
|
||||
@@ -6,7 +6,7 @@ title: Bulk Deletion
|
||||
|
||||
While deleting items individually via the API is supported, it can prove inefficient (time consuming) when multiple items are to be deleted sequentially.
|
||||
|
||||
For example, if the user wishes to delete a large number items (such as lines from a [Bill of Materials](../build/bom.md)), these items are deleted sequentially, with each `DELETE` separate request requiring network transfer, database access, cleanup, etc.
|
||||
For example, if the user wishes to delete a large number items (such as lines from a [Bill of Materials](../manufacturing/bom.md)), these items are deleted sequentially, with each `DELETE` separate request requiring network transfer, database access, cleanup, etc.
|
||||
|
||||
A much more efficient approach is to allow for "bulk deletion" of multiple database items in a single transaction. This means that only one network request is required, and only a single database access request.
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ title: Model Metadata
|
||||
|
||||
## Model Metadata
|
||||
|
||||
The API is *self describing* in that it provides metadata about the various fields available at any given endpoint. External applications (such as the [python interface](../api/python/python.md)) can introspect the API to determine information about the model fields.
|
||||
The API is *self describing* in that it provides metadata about the various fields available at any given endpoint. External applications (such as the [python interface](../api/python/index.md)) can introspect the API to determine information about the model fields.
|
||||
|
||||
!!! tip "API Forms"
|
||||
The various forms implemented in the InvenTree web interface make heavy use of this metadata feature
|
||||
@@ -13,7 +13,7 @@ The API is *self describing* in that it provides metadata about the various fiel
|
||||
|
||||
To request metadata about a particular API endpoint, simply perform an `OPTIONS` method request against the API URL.
|
||||
|
||||
For example, to view the metadata available for creating a new [Part Category](../part/part.md#part-category), an `OPTIONS` request to `/api/part/category/` yields:
|
||||
For example, to view the metadata available for creating a new [Part Category](../part/index.md#part-category), an `OPTIONS` request to `/api/part/category/` yields:
|
||||
|
||||
{% with id="api_cat_options", url="api/api_category_options.png", description="Part category options" %}
|
||||
{% include 'img.html' %}
|
||||
|
||||
@@ -6,7 +6,7 @@ title: Python Currency Support
|
||||
|
||||
InvenTree provides native support for multiple currencies, which can mean that data require conversion between these currencies, at defined exchange rates.
|
||||
|
||||
The InvenTree server maintains a set of exchange rates, which are updated periodically. These exchange rates are available via the [InvenTree API](../api.md), and can be used by the Python bindings.
|
||||
The InvenTree server maintains a set of exchange rates, which are updated periodically. These exchange rates are available via the [InvenTree API](../index.md), and can be used by the Python bindings.
|
||||
|
||||
### CurrencyManager Class
|
||||
|
||||
|
||||
@@ -67,7 +67,7 @@ print("Minimum stock:", part.minimum_stock)
|
||||
|
||||
### Adding Parameters
|
||||
|
||||
Each [part](../../part/part.md) can have multiple [parameters](../../part/parameter.md). For the example of the sofa (above) *length* and *weight* make sense. Each parameter has a parameter template that combines the parameter name with a unit. So we first have to create the parameter templates and afterwards add the parameter values to the sofa.
|
||||
Each [part](../../part/index.md) can have multiple [parameters](../../part/parameter.md). For the example of the sofa (above) *length* and *weight* make sense. Each parameter has a parameter template that combines the parameter name with a unit. So we first have to create the parameter templates and afterwards add the parameter values to the sofa.
|
||||
|
||||
```python
|
||||
from inventree.part import Parameter
|
||||
@@ -190,7 +190,7 @@ item.transferStock(loc, quantity=50)
|
||||
|
||||
### Delete a Part
|
||||
|
||||
To delete a [Part instance](../../part/part.md), first in needs to be marked as *inactive* (otherwise it will throw an error):
|
||||
To delete a [Part instance](../../part/index.md), first in needs to be marked as *inactive* (otherwise it will throw an error):
|
||||
|
||||
```python
|
||||
from inventree.part import Part
|
||||
|
||||
@@ -83,7 +83,7 @@ category = PartCategory(api, 10)
|
||||
|
||||
#### Multiple Items
|
||||
|
||||
Database items can be queried by using the `list` method for the given class. Note that arbitrary filter parameters can be applied (as specified by the [InvenTree API](../api.md)) to filter the returned results.
|
||||
Database items can be queried by using the `list` method for the given class. Note that arbitrary filter parameters can be applied (as specified by the [InvenTree API](../index.md)) to filter the returned results.
|
||||
|
||||
```python
|
||||
from inventree.part import Part
|
||||
@@ -7,7 +7,7 @@ The API schema as documented below is generated using the [drf-spectactular](htt
|
||||
|
||||
## API Version
|
||||
|
||||
This documentation is for API version: `315`
|
||||
This documentation is for API version: `339`
|
||||
|
||||
!!! tip "API Schema History"
|
||||
We track API schema changes, and provide a snapshot of each API schema version in the [API schema repository](https://github.com/inventree/schema/).
|
||||
|
||||
Reference in New Issue
Block a user