Lukas
2fea513c9c
This addresses issue #19 by making the implicit provider dependency order explicit and order-sensitive. Changes: 1. Created PROVIDER_ORDER.md - comprehensive documentation explaining: - The provider hierarchy from outermost to innermost - Why each provider must be at its position - Order-sensitive pitfalls and what would break - Guidelines for adding new providers in the future 2. Added provider composition tests (providerComposition.test.tsx): - 13 comprehensive tests validating provider order and dependencies - Tests verify all providers mount correctly - Tests check that hooks only work inside correct providers - Tests validate async initialization (AuthProvider, TimezoneProvider) - Tests verify theme persistence and notification propagation 3. Updated App.tsx with inline documentation: - Added detailed provider order contract in JSDoc header - Inline comments explaining each provider's position - Reference to PROVIDER_ORDER.md for detailed rationale 4. Updated Web-Development.md: - Added new section 5.5 'Provider Order Contract' - Documents provider hierarchy and rationale - Links to comprehensive provider documentation - References regression test suite All tests pass. TypeScript compilation succeeds. Build succeeds. The provider order is now explicit and future refactors can validate compliance through the regression test suite. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>