BeytullahCengiz88 afb1fa2883 Add CMFRT naming conventions, object ID ranges, and patterns documentation ... - Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity. - Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity. - Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods. - Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.		2026-07-14 14:09:04 +02:00
..
architecture	Add CMFRT naming conventions, object ID ranges, and patterns documentation	2026-07-14 14:09:04 +02:00
breaking-changes	Add CMFRT naming conventions, object ID ranges, and patterns documentation	2026-07-14 14:09:04 +02:00
events	Add CMFRT naming conventions, object ID ranges, and patterns documentation	2026-07-14 14:09:04 +02:00
naming	Add CMFRT naming conventions, object ID ranges, and patterns documentation	2026-07-14 14:09:04 +02:00
patterns	Add CMFRT naming conventions, object ID ranges, and patterns documentation	2026-07-14 14:09:04 +02:00
security	Add CMFRT naming conventions, object ID ranges, and patterns documentation	2026-07-14 14:09:04 +02:00
.gitkeep	Add initial project structure with .gitignore, LICENSE, README, and CODEOWNERS	2026-04-17 05:56:10 +02:00