2
0
mirror of https://github.com/inventree/InvenTree.git synced 2025-04-30 20:46:47 +00:00

Fix spelling of InvenTree in code base (#8561)

* fix spelling of InvenTree in code

* fix spelling in frontend
This commit is contained in:
Matthias Mair 2024-11-25 22:29:47 +01:00 committed by GitHub
parent 0fa7ed2742
commit 0f194af585
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
18 changed files with 24 additions and 24 deletions

View File

@ -1,7 +1,7 @@
# Example Caddyfile for Inventree # Example Caddyfile for InvenTree
# The following environment variables may be used: # The following environment variables may be used:
# - INVENTREE_SITE_URL: The upstream URL of the Inventree site (default: inventree.localhost) # - INVENTREE_SITE_URL: The upstream URL of the InvenTree site (default: inventree.localhost)
# - INVENTREE_SERVER: The internal URL of the Inventree container (default: http://inventree-server:8000) # - INVENTREE_SERVER: The internal URL of the InvenTree container (default: http://inventree-server:8000)
# #
# Note that while this file is a good starting point, it may need to be modified to suit your specific requirements # Note that while this file is a good starting point, it may need to be modified to suit your specific requirements

View File

@ -39,7 +39,7 @@ InvenTree allows you to upload simple BOM files in multiple formats, and downloa
## Build Parts ## Build Parts
Inventree features a build management system to help you track the progress of your builds. InvenTree features a build management system to help you track the progress of your builds.
Builds consume stock items to make new parts, you can decide to automatically or manually allocate parts from your current inventory. Builds consume stock items to make new parts, you can decide to automatically or manually allocate parts from your current inventory.
[Read more...](./build/build.md) [Read more...](./build/build.md)

View File

@ -61,7 +61,7 @@ A *contact* can be assigned to orders, (such as [purchase orders](./purchase_ord
A company can have multiple registered addresses for use with all types of orders. A company can have multiple registered addresses for use with all types of orders.
An address is broken down to internationally recognised elements that are designed to allow for formatting an address according to user needs. An address is broken down to internationally recognised elements that are designed to allow for formatting an address according to user needs.
Addresses are composed differently across the world, and Inventree reflects this by splitting addresses into components: Addresses are composed differently across the world, and InvenTree reflects this by splitting addresses into components:
- Line 1: Main street address - Line 1: Main street address
- Line 2: Extra street address line - Line 2: Extra street address line
- Postal Code: Also known as ZIP code, this is normally a number 3-5 digits in length - Postal Code: Also known as ZIP code, this is normally a number 3-5 digits in length

View File

@ -81,7 +81,7 @@ Multiple improvements have been made to the docker installation process, most no
### QR code scanner ### QR code scanner
[#2779](https://github.com/inventree/InvenTree/pull/2779) provides a QR code scanner which can be used to quickly scan Inventree generated QR codes using webcams or mobile devices. This feature requires secure (HTTPS) connection to the server. [#2779](https://github.com/inventree/InvenTree/pull/2779) provides a QR code scanner which can be used to quickly scan InvenTree generated QR codes using webcams or mobile devices. This feature requires secure (HTTPS) connection to the server.
### Order, Order ### Order, Order

View File

@ -63,7 +63,7 @@ Next you can start configuring the connection. Either use the config file or set
| `ldap.user_dn_template` | `INVENTREE_LDAP_USER_DN_TEMPLATE` | use direct bind as auth user, `ldap.bind_dn` and `ldap.bin_password` is not necessary then, e.g. `uid=%(user)s,dc=example,dc=org` | | `ldap.user_dn_template` | `INVENTREE_LDAP_USER_DN_TEMPLATE` | use direct bind as auth user, `ldap.bind_dn` and `ldap.bin_password` is not necessary then, e.g. `uid=%(user)s,dc=example,dc=org` |
| `ldap.global_options` | `INVENTREE_LDAP_GLOBAL_OPTIONS` | set advanced options as dict, e.g. TLS settings. For a list of all available options, see [python-ldap docs](https://www.python-ldap.org/en/latest/reference/ldap.html#ldap-options). (keys and values starting with OPT_ get automatically converted to `python-ldap` keys) | | `ldap.global_options` | `INVENTREE_LDAP_GLOBAL_OPTIONS` | set advanced options as dict, e.g. TLS settings. For a list of all available options, see [python-ldap docs](https://www.python-ldap.org/en/latest/reference/ldap.html#ldap-options). (keys and values starting with OPT_ get automatically converted to `python-ldap` keys) |
| `ldap.search_filter_str`| `INVENTREE_LDAP_SEARCH_FILTER_STR` | LDAP search filter str, default: `uid=%(user)s` | | `ldap.search_filter_str`| `INVENTREE_LDAP_SEARCH_FILTER_STR` | LDAP search filter str, default: `uid=%(user)s` |
| `ldap.user_attr_map` | `INVENTREE_LDAP_USER_ATTR_MAP` | LDAP <-> Inventree user attribute map, can be json if used as env, in yml directly specify the object. default: `{"first_name": "givenName", "last_name": "sn", "email": "mail"}` | | `ldap.user_attr_map` | `INVENTREE_LDAP_USER_ATTR_MAP` | LDAP <-> InvenTree user attribute map, can be json if used as env, in yml directly specify the object. default: `{"first_name": "givenName", "last_name": "sn", "email": "mail"}` |
| `ldap.always_update_user` | `INVENTREE_LDAP_ALWAYS_UPDATE_USER` | Always update the user on each login, default: `true` | | `ldap.always_update_user` | `INVENTREE_LDAP_ALWAYS_UPDATE_USER` | Always update the user on each login, default: `true` |
| `ldap.cache_timeout` | `INVENTREE_LDAP_CACHE_TIMEOUT` | cache timeout to reduce traffic with LDAP server, default: `3600` (1h) | | `ldap.cache_timeout` | `INVENTREE_LDAP_CACHE_TIMEOUT` | cache timeout to reduce traffic with LDAP server, default: `3600` (1h) |
| `ldap.group_search` | `INVENTREE_LDAP_GROUP_SEARCH` | Base LDAP DN for group searching; required to enable group features | | `ldap.group_search` | `INVENTREE_LDAP_GROUP_SEARCH` | Base LDAP DN for group searching; required to enable group features |

View File

@ -31,7 +31,7 @@ The installer creates the following directories:
| --- | --- | | --- | --- |
| `/etc/inventree/` | Configuration files | | `/etc/inventree/` | Configuration files |
| `/opt/inventree/` | InvenTree application files | | `/opt/inventree/` | InvenTree application files |
| `/opt/inventree/data/` | Inventree data files | | `/opt/inventree/data/` | InvenTree data files |
#### Performed steps #### Performed steps

View File

@ -68,7 +68,7 @@ python3 -m venv env
The virtual environment needs to be activated to ensure the correct python binaries and libraries are used. The InvenTree instructions assume that the virtual environment is always correctly activated. The virtual environment needs to be activated to ensure the correct python binaries and libraries are used. The InvenTree instructions assume that the virtual environment is always correctly activated.
To configure Inventree inside a virtual environment, ``cd`` into the inventree base directory and run the following command: To configure InvenTree inside a virtual environment, ``cd`` into the inventree base directory and run the following command:
``` ```
source env/bin/activate source env/bin/activate

View File

@ -100,4 +100,4 @@ InvenTree uses the [Redis](https://redis.io/) cache server to manage cache data.
To optimize and configure your redis deployment follow the [official docker guide](https://redis.io/docs/getting-started/install-stack/docker/#configuration). To optimize and configure your redis deployment follow the [official docker guide](https://redis.io/docs/getting-started/install-stack/docker/#configuration).
!!! tip "Enable Cache" !!! tip "Enable Cache"
While a redis container is provided in the default configuration, by default it is not enabled in the Inventree server. You can enable redis cache support by following the [caching configuration guide](./config.md#caching) While a redis container is provided in the default configuration, by default it is not enabled in the InvenTree server. You can enable redis cache support by following the [caching configuration guide](./config.md#caching)

View File

@ -99,7 +99,7 @@ class ClassProviderMixin:
@classmethod @classmethod
def get_is_builtin(cls): def get_is_builtin(cls):
"""Is this Class build in the Inventree source code?""" """Is this Class build in the InvenTree source code?"""
try: try:
Path(cls.get_provider_file()).relative_to(settings.BASE_DIR) Path(cls.get_provider_file()).relative_to(settings.BASE_DIR)
return True return True

View File

@ -1,4 +1,4 @@
"""The DigiKeyPlugin is meant to integrate the DigiKey API into Inventree. """The DigiKeyPlugin is meant to integrate the DigiKey API into InvenTree.
This plugin can currently only match DigiKey barcodes to supplier parts. This plugin can currently only match DigiKey barcodes to supplier parts.
""" """
@ -10,7 +10,7 @@ from plugin.mixins import SettingsMixin, SupplierBarcodeMixin
class DigiKeyPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin): class DigiKeyPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin):
"""Plugin to integrate the DigiKey API into Inventree.""" """Plugin to integrate the DigiKey API into InvenTree."""
NAME = 'DigiKeyPlugin' NAME = 'DigiKeyPlugin'
TITLE = _('Supplier Integration - DigiKey') TITLE = _('Supplier Integration - DigiKey')

View File

@ -1,4 +1,4 @@
"""The LCSCPlugin is meant to integrate the LCSC API into Inventree. """The LCSCPlugin is meant to integrate the LCSC API into InvenTree.
This plugin can currently only match LCSC barcodes to supplier parts. This plugin can currently only match LCSC barcodes to supplier parts.
""" """
@ -12,7 +12,7 @@ from plugin.mixins import SettingsMixin, SupplierBarcodeMixin
class LCSCPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin): class LCSCPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin):
"""Plugin to integrate the LCSC API into Inventree.""" """Plugin to integrate the LCSC API into InvenTree."""
NAME = 'LCSCPlugin' NAME = 'LCSCPlugin'
TITLE = _('Supplier Integration - LCSC') TITLE = _('Supplier Integration - LCSC')

View File

@ -1,4 +1,4 @@
"""The MouserPlugin is meant to integrate the Mouser API into Inventree. """The MouserPlugin is meant to integrate the Mouser API into InvenTree.
This plugin currently only match Mouser barcodes to supplier parts. This plugin currently only match Mouser barcodes to supplier parts.
""" """
@ -10,7 +10,7 @@ from plugin.mixins import SettingsMixin, SupplierBarcodeMixin
class MouserPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin): class MouserPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin):
"""Plugin to integrate the Mouser API into Inventree.""" """Plugin to integrate the Mouser API into InvenTree."""
NAME = 'MouserPlugin' NAME = 'MouserPlugin'
TITLE = _('Supplier Integration - Mouser') TITLE = _('Supplier Integration - Mouser')

View File

@ -1,4 +1,4 @@
"""The TMEPlugin is meant to integrate the TME API into Inventree. """The TMEPlugin is meant to integrate the TME API into InvenTree.
This plugin can currently only match TME barcodes to supplier parts. This plugin can currently only match TME barcodes to supplier parts.
""" """
@ -12,7 +12,7 @@ from plugin.mixins import SettingsMixin, SupplierBarcodeMixin
class TMEPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin): class TMEPlugin(SupplierBarcodeMixin, SettingsMixin, InvenTreePlugin):
"""Plugin to integrate the TME API into Inventree.""" """Plugin to integrate the TME API into InvenTree."""
NAME = 'TMEPlugin' NAME = 'TMEPlugin'
TITLE = _('Supplier Integration - TME') TITLE = _('Supplier Integration - TME')

View File

@ -38,7 +38,7 @@ export function getActions(navigate: NavigateFunction) {
{ {
id: 'server-info', id: 'server-info',
label: t`Server Information`, label: t`Server Information`,
description: t`About this Inventree instance`, description: t`About this InvenTree instance`,
onClick: () => serverInfo(), onClick: () => serverInfo(),
leftSection: <IconLink size='1.2rem' /> leftSection: <IconLink size='1.2rem' />
}, },

View File

@ -115,7 +115,7 @@ export function AboutLinks(): MenuLinkItem[] {
{ {
id: 'instance', id: 'instance',
title: t`System Information`, title: t`System Information`,
description: t`About this Inventree instance`, description: t`About this InvenTree instance`,
icon: 'info', icon: 'info',
action: serverInfo action: serverInfo
}, },

View File

@ -92,7 +92,7 @@ export interface SettingChoice {
} }
export enum SettingTyp { export enum SettingTyp {
Inventree = 'inventree', InvenTree = 'inventree',
Plugin = 'plugin', Plugin = 'plugin',
User = 'user', User = 'user',
Notification = 'notification' Notification = 'notification'

View File

@ -8,7 +8,7 @@ test('Modals as admin', async ({ page }) => {
await page.getByLabel('open-spotlight').click(); await page.getByLabel('open-spotlight').click();
await page await page
.getByRole('button', { .getByRole('button', {
name: 'Server Information About this Inventree instance' name: 'Server Information About this InvenTree instance'
}) })
.click(); .click();
await page.getByRole('cell', { name: 'Instance Name' }).waitFor(); await page.getByRole('cell', { name: 'Instance Name' }).waitFor();

View File

@ -49,7 +49,7 @@ test('Quick Command - No Keys', async ({ page }) => {
await page.getByLabel('open-spotlight').click(); await page.getByLabel('open-spotlight').click();
await page await page
.getByRole('button', { .getByRole('button', {
name: 'Server Information About this Inventree instance' name: 'Server Information About this InvenTree instance'
}) })
.click(); .click();
await page.getByRole('cell', { name: 'Instance Name' }).waitFor(); await page.getByRole('cell', { name: 'Instance Name' }).waitFor();