Mecalux/mcp-wms-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lint(standard): corrections completes mode standard

Browse Source 
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md,
  en-tete section Limagrain conserve)
- Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian)
- Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues),
  1 reciblee (manuel de reten)
- related: tenseflow -> tense-flow, pie -> mechanical-elements,
  group.md retire (doublon shipping)
- Registre: compteur global 122 -> 131 pages
- Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie)
- Aucun fichier limagrain/ modifie (cloisonnement)
This commit is contained in:
Arthur
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/modules/client-specific-rules.md
+5 -5
View File
@@ -2,7 +2,7 @@
title: "Client-Specific Rules"
type: module
sources:
- areas/client_specific_rules/index.md # 404 — source unavailable
- areas/client_specific_rules/index.md # 404 - source unavailable
related:
- modules/directives.md
- modules/owner-extensions.md
@@ -18,7 +18,7 @@ last_compiled: "2026-04-10"
Based on context from related modules, "Client-Specific Rules" appears to be either an alternate name or a superset concept for the **[[directives]]** module, which implements client-specific logistics customizations per owner and per account.
The Directives module documentation (sourced from `areas/directives/`) explicitly uses the title "Client-Specific Rules (_Directives_)" — suggesting these are the same capability.
The Directives module documentation (sourced from `areas/directives/`) explicitly uses the title "Client-Specific Rules (_Directives_)" - suggesting these are the same capability.
## What is covered by this concept
@@ -32,6 +32,6 @@ Client-specific rules in EasyWMS are implemented through two mechanisms:
## Related
- [[directives]] — The primary implementation of client-specific rules in EasyWMS (owner directives and account directives)
- [[owner-extensions]] — Prerequisite module enabling owner-level data isolation
- [[billing-3pl]] — Client-specific billing rules and contracts
- [[directives]] - The primary implementation of client-specific rules in EasyWMS (owner directives and account directives)
- [[owner-extensions]] - Prerequisite module enabling owner-level data isolation
- [[billing-3pl]] - Client-specific billing rules and contracts