bc-code-intelligence-mcp 1.6.0 → 1.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +20 -20
- package/README.md +165 -165
- package/dist/config/config-loader.js +6 -6
- package/dist/config/config-loader.js.map +1 -1
- package/dist/layers/embedded-layer.js +29 -29
- package/dist/layers/git-layer.d.ts +2 -0
- package/dist/layers/git-layer.d.ts.map +1 -1
- package/dist/layers/git-layer.js +47 -14
- package/dist/layers/git-layer.js.map +1 -1
- package/dist/layers/project-layer.js +33 -33
- package/dist/services/methodology-service.js +28 -28
- package/dist/services/multi-content-layer-service.d.ts +5 -0
- package/dist/services/multi-content-layer-service.d.ts.map +1 -1
- package/dist/services/multi-content-layer-service.js +31 -0
- package/dist/services/multi-content-layer-service.js.map +1 -1
- package/dist/tools/create_layer_content/handler.js +83 -83
- package/dist/tools/scaffold_layer_repo/handler.js +276 -276
- package/dist/tools/workflow_batch/schema.js +9 -9
- package/dist/tools/workflow_cancel/schema.js +9 -9
- package/dist/tools/workflow_complete/schema.js +9 -9
- package/dist/tools/workflow_list/schema.js +11 -11
- package/dist/tools/workflow_next/schema.js +8 -8
- package/dist/tools/workflow_progress/schema.js +5 -5
- package/dist/tools/workflow_start/schema.js +14 -14
- package/dist/tools/workflow_status/schema.js +8 -8
- package/embedded-knowledge/.github/ISSUE_TEMPLATE/bug-report.md +23 -23
- package/embedded-knowledge/.github/ISSUE_TEMPLATE/content-improvement.md +23 -23
- package/embedded-knowledge/.github/ISSUE_TEMPLATE/knowledge-request.md +29 -29
- package/embedded-knowledge/AGENTS.md +177 -177
- package/embedded-knowledge/CONTRIBUTING.md +57 -57
- package/embedded-knowledge/LICENSE +20 -20
- package/embedded-knowledge/README.md +31 -31
- package/embedded-knowledge/codelens-mappings.yaml +111 -111
- package/embedded-knowledge/domains/shared/al-file-naming-conventions.md +155 -155
- package/embedded-knowledge/scripts/frontmatter_validator.ps1 +330 -330
- package/embedded-knowledge/workflows/bc-version-upgrade.yaml +160 -160
- package/embedded-knowledge/workflows/code-review.yaml +148 -148
- package/embedded-knowledge/workflows/error-to-errorinfo-migration.yaml +137 -137
- package/embedded-knowledge/workflows/onboarding.yaml +124 -124
- package/embedded-knowledge/workflows/performance-audit.yaml +148 -148
- package/embedded-knowledge/workflows/proposal-review.yaml +117 -117
- package/embedded-knowledge/workflows/security-audit.yaml +139 -139
- package/package.json +83 -83
- package/dist/services/roleplay-engine.d.ts +0 -169
- package/dist/services/roleplay-engine.d.ts.map +0 -1
- package/dist/services/roleplay-engine.js +0 -1026
- package/dist/services/roleplay-engine.js.map +0 -1
- package/dist/streamlined-handlers.d.ts +0 -8
- package/dist/streamlined-handlers.d.ts.map +0 -1
- package/dist/streamlined-handlers.js +0 -29
- package/dist/streamlined-handlers.js.map +0 -1
- package/dist/tools/advance_workflow/handler.d.ts +0 -21
- package/dist/tools/advance_workflow/handler.d.ts.map +0 -1
- package/dist/tools/advance_workflow/handler.js +0 -58
- package/dist/tools/advance_workflow/handler.js.map +0 -1
- package/dist/tools/advance_workflow/schema.d.ts +0 -8
- package/dist/tools/advance_workflow/schema.d.ts.map +0 -1
- package/dist/tools/advance_workflow/schema.js +0 -28
- package/dist/tools/advance_workflow/schema.js.map +0 -1
- package/dist/tools/config-diagnostic-tools.d.ts +0 -234
- package/dist/tools/config-diagnostic-tools.d.ts.map +0 -1
- package/dist/tools/config-diagnostic-tools.js +0 -887
- package/dist/tools/config-diagnostic-tools.js.map +0 -1
- package/dist/tools/context-snapshot/handler.d.ts +0 -14
- package/dist/tools/context-snapshot/handler.d.ts.map +0 -1
- package/dist/tools/context-snapshot/handler.js +0 -143
- package/dist/tools/context-snapshot/handler.js.map +0 -1
- package/dist/tools/context-snapshot/schema.d.ts +0 -11
- package/dist/tools/context-snapshot/schema.d.ts.map +0 -1
- package/dist/tools/context-snapshot/schema.js +0 -46
- package/dist/tools/context-snapshot/schema.js.map +0 -1
- package/dist/tools/core-tools.d.ts +0 -26
- package/dist/tools/core-tools.d.ts.map +0 -1
- package/dist/tools/core-tools.js +0 -262
- package/dist/tools/core-tools.js.map +0 -1
- package/dist/tools/get_workflow_help/handler.d.ts +0 -12
- package/dist/tools/get_workflow_help/handler.d.ts.map +0 -1
- package/dist/tools/get_workflow_help/handler.js +0 -54
- package/dist/tools/get_workflow_help/handler.js.map +0 -1
- package/dist/tools/get_workflow_help/schema.d.ts +0 -8
- package/dist/tools/get_workflow_help/schema.d.ts.map +0 -1
- package/dist/tools/get_workflow_help/schema.js +0 -25
- package/dist/tools/get_workflow_help/schema.js.map +0 -1
- package/dist/tools/handoff-tools.d.ts +0 -37
- package/dist/tools/handoff-tools.d.ts.map +0 -1
- package/dist/tools/handoff-tools.js +0 -265
- package/dist/tools/handoff-tools.js.map +0 -1
- package/dist/tools/knowledge-query/handler.d.ts +0 -29
- package/dist/tools/knowledge-query/handler.d.ts.map +0 -1
- package/dist/tools/knowledge-query/handler.js +0 -85
- package/dist/tools/knowledge-query/handler.js.map +0 -1
- package/dist/tools/knowledge-query/schema.d.ts +0 -12
- package/dist/tools/knowledge-query/schema.d.ts.map +0 -1
- package/dist/tools/knowledge-query/schema.js +0 -64
- package/dist/tools/knowledge-query/schema.js.map +0 -1
- package/dist/tools/onboarding-tools.d.ts +0 -43
- package/dist/tools/onboarding-tools.d.ts.map +0 -1
- package/dist/tools/onboarding-tools.js +0 -353
- package/dist/tools/onboarding-tools.js.map +0 -1
- package/dist/tools/specialist-consult/handler.d.ts +0 -23
- package/dist/tools/specialist-consult/handler.d.ts.map +0 -1
- package/dist/tools/specialist-consult/handler.js +0 -120
- package/dist/tools/specialist-consult/handler.js.map +0 -1
- package/dist/tools/specialist-consult/schema.d.ts +0 -11
- package/dist/tools/specialist-consult/schema.d.ts.map +0 -1
- package/dist/tools/specialist-consult/schema.js +0 -47
- package/dist/tools/specialist-consult/schema.js.map +0 -1
- package/dist/tools/specialist-discovery-tools.d.ts +0 -27
- package/dist/tools/specialist-discovery-tools.d.ts.map +0 -1
- package/dist/tools/specialist-discovery-tools.js +0 -281
- package/dist/tools/specialist-discovery-tools.js.map +0 -1
- package/dist/tools/specialist-list/handler.d.ts +0 -14
- package/dist/tools/specialist-list/handler.d.ts.map +0 -1
- package/dist/tools/specialist-list/handler.js +0 -70
- package/dist/tools/specialist-list/handler.js.map +0 -1
- package/dist/tools/specialist-list/schema.d.ts +0 -11
- package/dist/tools/specialist-list/schema.d.ts.map +0 -1
- package/dist/tools/specialist-list/schema.js +0 -29
- package/dist/tools/specialist-list/schema.js.map +0 -1
- package/dist/tools/start_bc_workflow/handler.d.ts +0 -21
- package/dist/tools/start_bc_workflow/handler.d.ts.map +0 -1
- package/dist/tools/start_bc_workflow/handler.js +0 -237
- package/dist/tools/start_bc_workflow/handler.js.map +0 -1
- package/dist/tools/start_bc_workflow/schema.d.ts +0 -8
- package/dist/tools/start_bc_workflow/schema.d.ts.map +0 -1
- package/dist/tools/start_bc_workflow/schema.js +0 -43
- package/dist/tools/start_bc_workflow/schema.js.map +0 -1
- package/dist/tools/workflow-execute/handler.d.ts +0 -44
- package/dist/tools/workflow-execute/handler.d.ts.map +0 -1
- package/dist/tools/workflow-execute/handler.js +0 -333
- package/dist/tools/workflow-execute/handler.js.map +0 -1
- package/dist/tools/workflow-execute/schema.d.ts +0 -13
- package/dist/tools/workflow-execute/schema.d.ts.map +0 -1
- package/dist/tools/workflow-execute/schema.js +0 -108
- package/dist/tools/workflow-execute/schema.js.map +0 -1
- package/dist/tools/workflow_start_v2/handler.d.ts +0 -21
- package/dist/tools/workflow_start_v2/handler.d.ts.map +0 -1
- package/dist/tools/workflow_start_v2/handler.js +0 -133
- package/dist/tools/workflow_start_v2/handler.js.map +0 -1
- package/dist/tools/workflow_start_v2/schema.d.ts +0 -8
- package/dist/tools/workflow_start_v2/schema.d.ts.map +0 -1
- package/dist/tools/workflow_start_v2/schema.js +0 -102
- package/dist/tools/workflow_start_v2/schema.js.map +0 -1
- package/dist/tools/workspace-tools.d.ts +0 -96
- package/dist/tools/workspace-tools.d.ts.map +0 -1
- package/dist/tools/workspace-tools.js +0 -188
- package/dist/tools/workspace-tools.js.map +0 -1
- package/dist/types/roleplay-types.d.ts +0 -156
- package/dist/types/roleplay-types.d.ts.map +0 -1
- package/dist/types/roleplay-types.js +0 -8
- package/dist/types/roleplay-types.js.map +0 -1
- package/dist/workflows/domain-workflows.d.ts +0 -8
- package/dist/workflows/domain-workflows.d.ts.map +0 -1
- package/dist/workflows/domain-workflows.js +0 -360
- package/dist/workflows/domain-workflows.js.map +0 -1
|
@@ -1,58 +1,58 @@
|
|
|
1
|
-
# Contributing to Business Central Knowledge Base
|
|
2
|
-
|
|
3
|
-
## Overview
|
|
4
|
-
This repository contains pure knowledge content for Business Central best practices. All content is markdown with YAML frontmatter.
|
|
5
|
-
|
|
6
|
-
## Content Standards
|
|
7
|
-
|
|
8
|
-
### File Structure
|
|
9
|
-
Each knowledge topic follows this structure:
|
|
10
|
-
```markdown
|
|
11
|
-
---
|
|
12
|
-
title: "Topic Title"
|
|
13
|
-
domain: "performance"
|
|
14
|
-
difficulty: "intermediate"
|
|
15
|
-
bc_versions: "14+"
|
|
16
|
-
tags: ["sift", "optimization", "database"]
|
|
17
|
-
related_topics: ["topic-id-1", "topic-id-2"]
|
|
18
|
-
---
|
|
19
|
-
|
|
20
|
-
# Topic Title
|
|
21
|
-
|
|
22
|
-
Content here following established patterns...
|
|
23
|
-
```
|
|
24
|
-
|
|
25
|
-
### Quality Requirements
|
|
26
|
-
- **Atomic Focus**: One concept per file
|
|
27
|
-
- **BC Version Compatibility**: Always specify version ranges
|
|
28
|
-
- **Complete Frontmatter**: All required YAML fields present
|
|
29
|
-
- **Cross-References**: Link to related topics where appropriate
|
|
30
|
-
- **Consistent Formatting**: Follow existing markdown patterns
|
|
31
|
-
|
|
32
|
-
## Submission Process
|
|
33
|
-
1. Fork the repository
|
|
34
|
-
2. Create content following established patterns in appropriate domain directory
|
|
35
|
-
3. Ensure YAML frontmatter is complete and valid
|
|
36
|
-
4. Test that internal links work correctly
|
|
37
|
-
5. Submit pull request with clear description of the knowledge added/updated
|
|
38
|
-
|
|
39
|
-
## Content Validation
|
|
40
|
-
Pull requests are automatically validated for:
|
|
41
|
-
- YAML frontmatter completeness
|
|
42
|
-
- BC version compatibility format
|
|
43
|
-
- Internal link integrity
|
|
44
|
-
- Proper domain/directory placement
|
|
45
|
-
- Markdown formatting consistency
|
|
46
|
-
|
|
47
|
-
## Domain Organization
|
|
48
|
-
Place content in appropriate domain directories:
|
|
49
|
-
- `domains/performance/` - Performance optimization
|
|
50
|
-
- `domains/api-design/` - REST/OData patterns
|
|
51
|
-
- `domains/security/` - Authentication/authorization
|
|
52
|
-
- `domains/data-architecture/` - Table design
|
|
53
|
-
- [See full domain list in repository structure]
|
|
54
|
-
|
|
55
|
-
## Getting Help
|
|
56
|
-
- Review existing topics for patterns
|
|
57
|
-
- Check AGENTS.md for AI assistant guidance
|
|
1
|
+
# Contributing to Business Central Knowledge Base
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
This repository contains pure knowledge content for Business Central best practices. All content is markdown with YAML frontmatter.
|
|
5
|
+
|
|
6
|
+
## Content Standards
|
|
7
|
+
|
|
8
|
+
### File Structure
|
|
9
|
+
Each knowledge topic follows this structure:
|
|
10
|
+
```markdown
|
|
11
|
+
---
|
|
12
|
+
title: "Topic Title"
|
|
13
|
+
domain: "performance"
|
|
14
|
+
difficulty: "intermediate"
|
|
15
|
+
bc_versions: "14+"
|
|
16
|
+
tags: ["sift", "optimization", "database"]
|
|
17
|
+
related_topics: ["topic-id-1", "topic-id-2"]
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
# Topic Title
|
|
21
|
+
|
|
22
|
+
Content here following established patterns...
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
### Quality Requirements
|
|
26
|
+
- **Atomic Focus**: One concept per file
|
|
27
|
+
- **BC Version Compatibility**: Always specify version ranges
|
|
28
|
+
- **Complete Frontmatter**: All required YAML fields present
|
|
29
|
+
- **Cross-References**: Link to related topics where appropriate
|
|
30
|
+
- **Consistent Formatting**: Follow existing markdown patterns
|
|
31
|
+
|
|
32
|
+
## Submission Process
|
|
33
|
+
1. Fork the repository
|
|
34
|
+
2. Create content following established patterns in appropriate domain directory
|
|
35
|
+
3. Ensure YAML frontmatter is complete and valid
|
|
36
|
+
4. Test that internal links work correctly
|
|
37
|
+
5. Submit pull request with clear description of the knowledge added/updated
|
|
38
|
+
|
|
39
|
+
## Content Validation
|
|
40
|
+
Pull requests are automatically validated for:
|
|
41
|
+
- YAML frontmatter completeness
|
|
42
|
+
- BC version compatibility format
|
|
43
|
+
- Internal link integrity
|
|
44
|
+
- Proper domain/directory placement
|
|
45
|
+
- Markdown formatting consistency
|
|
46
|
+
|
|
47
|
+
## Domain Organization
|
|
48
|
+
Place content in appropriate domain directories:
|
|
49
|
+
- `domains/performance/` - Performance optimization
|
|
50
|
+
- `domains/api-design/` - REST/OData patterns
|
|
51
|
+
- `domains/security/` - Authentication/authorization
|
|
52
|
+
- `domains/data-architecture/` - Table design
|
|
53
|
+
- [See full domain list in repository structure]
|
|
54
|
+
|
|
55
|
+
## Getting Help
|
|
56
|
+
- Review existing topics for patterns
|
|
57
|
+
- Check AGENTS.md for AI assistant guidance
|
|
58
58
|
- Open issues for questions about content organization
|
|
@@ -1,21 +1,21 @@
|
|
|
1
|
-
MIT License
|
|
2
|
-
|
|
3
|
-
Copyright (c) 2024 Business Central Knowledge Base
|
|
4
|
-
|
|
5
|
-
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
-
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
-
in the Software without restriction, including without limitation the rights
|
|
8
|
-
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
-
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
-
furnished to do so, subject to the following conditions:
|
|
11
|
-
|
|
12
|
-
The above copyright notice and this permission notice shall be included in all
|
|
13
|
-
copies or substantial portions of the Software.
|
|
14
|
-
|
|
15
|
-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
-
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
-
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
-
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
-
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
-
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2024 Business Central Knowledge Base
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
21
|
SOFTWARE.
|
|
@@ -1,32 +1,32 @@
|
|
|
1
|
-
# BC Code Intelligence Knowledge Base
|
|
2
|
-
|
|
3
|
-
Pure knowledge content repository for Business Central best practices, methodologies, and domain expertise.
|
|
4
|
-
|
|
5
|
-
## Structure
|
|
6
|
-
- `/domains/` - 24 BC domains with 87+ atomic knowledge topics
|
|
7
|
-
- `/methodologies/` - AI workflow frameworks for systematic optimization
|
|
8
|
-
- `/specialists/` - 14 AI persona definitions for focused expertise
|
|
9
|
-
- `/prompts/` - Strategic prompts for common BC scenarios
|
|
10
|
-
|
|
11
|
-
## Specialists
|
|
12
|
-
Complete roster of 14 BC development specialists:
|
|
13
|
-
- **Alex Architect** - Strategic Planning & Architecture
|
|
14
|
-
- **Casey Copilot** - AI-Enhanced Development Coach
|
|
15
|
-
- **Dean Debug** - Performance & Troubleshooting
|
|
16
|
-
- **Eva Errors** - Error Handling & Exception Management
|
|
17
|
-
- **Jordan Bridge** - Systems Connection & Event-Driven Design
|
|
18
|
-
- **Logan Legacy** - Legacy Code & Version Migration
|
|
19
|
-
- **Maya Mentor** - Learning & Skill Development
|
|
20
|
-
- **Morgan Market** - AppSource & ISV Business Expert
|
|
21
|
-
- **Quinn Tester** - Quality Validation & Test Design
|
|
22
|
-
- **Roger Reviewer** - Code Quality & Review Standards
|
|
23
|
-
- **Sam Coder** - Efficient Implementation Expert
|
|
24
|
-
- **Seth Security** - Security & Permission Management
|
|
25
|
-
- **Taylor Docs** - Documentation & Knowledge Management
|
|
26
|
-
- **Uma UX** - User Experience & Interface Design
|
|
27
|
-
|
|
28
|
-
## Usage
|
|
29
|
-
This repository is consumed by the BC Code Intelligence MCP server via git submodule. Content is pure markdown with YAML frontmatter.
|
|
30
|
-
|
|
31
|
-
## Contributing
|
|
1
|
+
# BC Code Intelligence Knowledge Base
|
|
2
|
+
|
|
3
|
+
Pure knowledge content repository for Business Central best practices, methodologies, and domain expertise.
|
|
4
|
+
|
|
5
|
+
## Structure
|
|
6
|
+
- `/domains/` - 24 BC domains with 87+ atomic knowledge topics
|
|
7
|
+
- `/methodologies/` - AI workflow frameworks for systematic optimization
|
|
8
|
+
- `/specialists/` - 14 AI persona definitions for focused expertise
|
|
9
|
+
- `/prompts/` - Strategic prompts for common BC scenarios
|
|
10
|
+
|
|
11
|
+
## Specialists
|
|
12
|
+
Complete roster of 14 BC development specialists:
|
|
13
|
+
- **Alex Architect** - Strategic Planning & Architecture
|
|
14
|
+
- **Casey Copilot** - AI-Enhanced Development Coach
|
|
15
|
+
- **Dean Debug** - Performance & Troubleshooting
|
|
16
|
+
- **Eva Errors** - Error Handling & Exception Management
|
|
17
|
+
- **Jordan Bridge** - Systems Connection & Event-Driven Design
|
|
18
|
+
- **Logan Legacy** - Legacy Code & Version Migration
|
|
19
|
+
- **Maya Mentor** - Learning & Skill Development
|
|
20
|
+
- **Morgan Market** - AppSource & ISV Business Expert
|
|
21
|
+
- **Quinn Tester** - Quality Validation & Test Design
|
|
22
|
+
- **Roger Reviewer** - Code Quality & Review Standards
|
|
23
|
+
- **Sam Coder** - Efficient Implementation Expert
|
|
24
|
+
- **Seth Security** - Security & Permission Management
|
|
25
|
+
- **Taylor Docs** - Documentation & Knowledge Management
|
|
26
|
+
- **Uma UX** - User Experience & Interface Design
|
|
27
|
+
|
|
28
|
+
## Usage
|
|
29
|
+
This repository is consumed by the BC Code Intelligence MCP server via git submodule. Content is pure markdown with YAML frontmatter.
|
|
30
|
+
|
|
31
|
+
## Contributing
|
|
32
32
|
See [CONTRIBUTING.md](CONTRIBUTING.md) for content standards and submission process.
|
|
@@ -1,111 +1,111 @@
|
|
|
1
|
-
# CodeLens Pattern-to-Specialist Mappings
|
|
2
|
-
# These patterns are matched against AL code to suggest relevant specialists
|
|
3
|
-
|
|
4
|
-
mappings:
|
|
5
|
-
# Error handling -> Eva
|
|
6
|
-
- pattern: "\\bError\\s*\\("
|
|
7
|
-
specialist: eva-errors
|
|
8
|
-
label: "Ask Eva about ErrorInfo"
|
|
9
|
-
|
|
10
|
-
- pattern: "\\bMessage\\s*\\("
|
|
11
|
-
specialist: eva-errors
|
|
12
|
-
label: "Review messaging with Eva"
|
|
13
|
-
|
|
14
|
-
- pattern: "\\bFieldError\\s*\\("
|
|
15
|
-
specialist: eva-errors
|
|
16
|
-
label: "FieldError guidance from Eva"
|
|
17
|
-
|
|
18
|
-
- pattern: "\\bTestField\\s*\\("
|
|
19
|
-
specialist: eva-errors
|
|
20
|
-
label: "TestField patterns with Eva"
|
|
21
|
-
|
|
22
|
-
# Events and integration -> Jordan
|
|
23
|
-
- pattern: "OnBefore|OnAfter|\\[EventSubscriber"
|
|
24
|
-
specialist: jordan-bridge
|
|
25
|
-
label: "Review with Jordan"
|
|
26
|
-
|
|
27
|
-
- pattern: "HttpClient|WebServiceActionContext"
|
|
28
|
-
specialist: jordan-bridge
|
|
29
|
-
label: "Integration review with Jordan"
|
|
30
|
-
|
|
31
|
-
- pattern: "\\[IntegrationEvent"
|
|
32
|
-
specialist: jordan-bridge
|
|
33
|
-
label: "Event design with Jordan"
|
|
34
|
-
|
|
35
|
-
# Security -> Seth
|
|
36
|
-
- pattern: "TableData|RIMD|Permissions"
|
|
37
|
-
specialist: seth-security
|
|
38
|
-
label: "Security review with Seth"
|
|
39
|
-
|
|
40
|
-
- pattern: "\\[Scope\\s*\\("
|
|
41
|
-
specialist: seth-security
|
|
42
|
-
label: "Scope review with Seth"
|
|
43
|
-
|
|
44
|
-
- pattern: "\\[InherentPermissions"
|
|
45
|
-
specialist: seth-security
|
|
46
|
-
label: "InherentPermissions with Seth"
|
|
47
|
-
|
|
48
|
-
- pattern: "\\[InherentEntitlements"
|
|
49
|
-
specialist: seth-security
|
|
50
|
-
label: "Entitlements review with Seth"
|
|
51
|
-
|
|
52
|
-
# Testing -> Quinn
|
|
53
|
-
- pattern: "\\[Test\\]"
|
|
54
|
-
specialist: quinn-tester
|
|
55
|
-
label: "Ask Quinn about testing"
|
|
56
|
-
|
|
57
|
-
- pattern: "\\[TestPermissions"
|
|
58
|
-
specialist: quinn-tester
|
|
59
|
-
label: "Test permissions with Quinn"
|
|
60
|
-
|
|
61
|
-
- pattern: "\\[HandlerFunctions"
|
|
62
|
-
specialist: quinn-tester
|
|
63
|
-
label: "Handler functions with Quinn"
|
|
64
|
-
|
|
65
|
-
- pattern: "LibraryAssert|Assert\\."
|
|
66
|
-
specialist: quinn-tester
|
|
67
|
-
label: "Assertions with Quinn"
|
|
68
|
-
|
|
69
|
-
# Performance -> Dean
|
|
70
|
-
- pattern: "FindSet|FindFirst|ModifyAll"
|
|
71
|
-
specialist: dean-debug
|
|
72
|
-
label: "Performance review with Dean"
|
|
73
|
-
|
|
74
|
-
- pattern: "SetLoadFields|SetAutoCalcFields"
|
|
75
|
-
specialist: dean-debug
|
|
76
|
-
label: "SIFT/performance with Dean"
|
|
77
|
-
|
|
78
|
-
- pattern: "CalcFields|CalcSums"
|
|
79
|
-
specialist: dean-debug
|
|
80
|
-
label: "CalcFields optimization with Dean"
|
|
81
|
-
|
|
82
|
-
- pattern: "LogMessage|Session\\.LogMessage"
|
|
83
|
-
specialist: dean-debug
|
|
84
|
-
label: "Telemetry with Dean"
|
|
85
|
-
|
|
86
|
-
# Documentation -> Taylor
|
|
87
|
-
- pattern: "/// <summary>"
|
|
88
|
-
specialist: taylor-docs
|
|
89
|
-
label: "Documentation with Taylor"
|
|
90
|
-
|
|
91
|
-
- pattern: "/// <param"
|
|
92
|
-
specialist: taylor-docs
|
|
93
|
-
label: "Parameter docs with Taylor"
|
|
94
|
-
|
|
95
|
-
# Architecture -> Alex
|
|
96
|
-
- pattern: "codeunit \\d+|table \\d+"
|
|
97
|
-
specialist: alex-architect
|
|
98
|
-
label: "Architecture with Alex"
|
|
99
|
-
|
|
100
|
-
- pattern: "\\[Obsolete"
|
|
101
|
-
specialist: alex-architect
|
|
102
|
-
label: "Deprecation strategy with Alex"
|
|
103
|
-
|
|
104
|
-
- pattern: "interface "
|
|
105
|
-
specialist: alex-architect
|
|
106
|
-
label: "Interface design with Alex"
|
|
107
|
-
|
|
108
|
-
# Code quality -> Roger
|
|
109
|
-
- pattern: "procedure .+\\("
|
|
110
|
-
specialist: roger-reviewer
|
|
111
|
-
label: "Code review with Roger"
|
|
1
|
+
# CodeLens Pattern-to-Specialist Mappings
|
|
2
|
+
# These patterns are matched against AL code to suggest relevant specialists
|
|
3
|
+
|
|
4
|
+
mappings:
|
|
5
|
+
# Error handling -> Eva
|
|
6
|
+
- pattern: "\\bError\\s*\\("
|
|
7
|
+
specialist: eva-errors
|
|
8
|
+
label: "Ask Eva about ErrorInfo"
|
|
9
|
+
|
|
10
|
+
- pattern: "\\bMessage\\s*\\("
|
|
11
|
+
specialist: eva-errors
|
|
12
|
+
label: "Review messaging with Eva"
|
|
13
|
+
|
|
14
|
+
- pattern: "\\bFieldError\\s*\\("
|
|
15
|
+
specialist: eva-errors
|
|
16
|
+
label: "FieldError guidance from Eva"
|
|
17
|
+
|
|
18
|
+
- pattern: "\\bTestField\\s*\\("
|
|
19
|
+
specialist: eva-errors
|
|
20
|
+
label: "TestField patterns with Eva"
|
|
21
|
+
|
|
22
|
+
# Events and integration -> Jordan
|
|
23
|
+
- pattern: "OnBefore|OnAfter|\\[EventSubscriber"
|
|
24
|
+
specialist: jordan-bridge
|
|
25
|
+
label: "Review with Jordan"
|
|
26
|
+
|
|
27
|
+
- pattern: "HttpClient|WebServiceActionContext"
|
|
28
|
+
specialist: jordan-bridge
|
|
29
|
+
label: "Integration review with Jordan"
|
|
30
|
+
|
|
31
|
+
- pattern: "\\[IntegrationEvent"
|
|
32
|
+
specialist: jordan-bridge
|
|
33
|
+
label: "Event design with Jordan"
|
|
34
|
+
|
|
35
|
+
# Security -> Seth
|
|
36
|
+
- pattern: "TableData|RIMD|Permissions"
|
|
37
|
+
specialist: seth-security
|
|
38
|
+
label: "Security review with Seth"
|
|
39
|
+
|
|
40
|
+
- pattern: "\\[Scope\\s*\\("
|
|
41
|
+
specialist: seth-security
|
|
42
|
+
label: "Scope review with Seth"
|
|
43
|
+
|
|
44
|
+
- pattern: "\\[InherentPermissions"
|
|
45
|
+
specialist: seth-security
|
|
46
|
+
label: "InherentPermissions with Seth"
|
|
47
|
+
|
|
48
|
+
- pattern: "\\[InherentEntitlements"
|
|
49
|
+
specialist: seth-security
|
|
50
|
+
label: "Entitlements review with Seth"
|
|
51
|
+
|
|
52
|
+
# Testing -> Quinn
|
|
53
|
+
- pattern: "\\[Test\\]"
|
|
54
|
+
specialist: quinn-tester
|
|
55
|
+
label: "Ask Quinn about testing"
|
|
56
|
+
|
|
57
|
+
- pattern: "\\[TestPermissions"
|
|
58
|
+
specialist: quinn-tester
|
|
59
|
+
label: "Test permissions with Quinn"
|
|
60
|
+
|
|
61
|
+
- pattern: "\\[HandlerFunctions"
|
|
62
|
+
specialist: quinn-tester
|
|
63
|
+
label: "Handler functions with Quinn"
|
|
64
|
+
|
|
65
|
+
- pattern: "LibraryAssert|Assert\\."
|
|
66
|
+
specialist: quinn-tester
|
|
67
|
+
label: "Assertions with Quinn"
|
|
68
|
+
|
|
69
|
+
# Performance -> Dean
|
|
70
|
+
- pattern: "FindSet|FindFirst|ModifyAll"
|
|
71
|
+
specialist: dean-debug
|
|
72
|
+
label: "Performance review with Dean"
|
|
73
|
+
|
|
74
|
+
- pattern: "SetLoadFields|SetAutoCalcFields"
|
|
75
|
+
specialist: dean-debug
|
|
76
|
+
label: "SIFT/performance with Dean"
|
|
77
|
+
|
|
78
|
+
- pattern: "CalcFields|CalcSums"
|
|
79
|
+
specialist: dean-debug
|
|
80
|
+
label: "CalcFields optimization with Dean"
|
|
81
|
+
|
|
82
|
+
- pattern: "LogMessage|Session\\.LogMessage"
|
|
83
|
+
specialist: dean-debug
|
|
84
|
+
label: "Telemetry with Dean"
|
|
85
|
+
|
|
86
|
+
# Documentation -> Taylor
|
|
87
|
+
- pattern: "/// <summary>"
|
|
88
|
+
specialist: taylor-docs
|
|
89
|
+
label: "Documentation with Taylor"
|
|
90
|
+
|
|
91
|
+
- pattern: "/// <param"
|
|
92
|
+
specialist: taylor-docs
|
|
93
|
+
label: "Parameter docs with Taylor"
|
|
94
|
+
|
|
95
|
+
# Architecture -> Alex
|
|
96
|
+
- pattern: "codeunit \\d+|table \\d+"
|
|
97
|
+
specialist: alex-architect
|
|
98
|
+
label: "Architecture with Alex"
|
|
99
|
+
|
|
100
|
+
- pattern: "\\[Obsolete"
|
|
101
|
+
specialist: alex-architect
|
|
102
|
+
label: "Deprecation strategy with Alex"
|
|
103
|
+
|
|
104
|
+
- pattern: "interface "
|
|
105
|
+
specialist: alex-architect
|
|
106
|
+
label: "Interface design with Alex"
|
|
107
|
+
|
|
108
|
+
# Code quality -> Roger
|
|
109
|
+
- pattern: "procedure .+\\("
|
|
110
|
+
specialist: roger-reviewer
|
|
111
|
+
label: "Code review with Roger"
|