Open paulfryer opened 14 hours ago
Property | Value |
---|---|
Proposed Branch Name | implement-capability-process-typescript |
Total Files in Scope | 19 |
Estimated Input Tokens | 9838 |
```text * !.* ```
| File | Estimated Tokens | |------|------------------| | LICENSE | 2972 | | sqlserver-to-postgress-migration/migration-report.md | 1137 | | sqlserver-to-postgress-migration/migration-app/Program.cs | 573 | | README.md | 495 | | sqlserver-to-postgress-migration/postgress/tables/SalesOrderHeader.sql | 380 | | adventureworks/tables/SalesOrderHeader.sql | 275 | | sqlserver-to-postgress-migration/postgress/tables/Product.sql | 273 | | adventureworks/tables/Product.sql | 228 | | sqlserver-to-postgress-migration/postgress/tables/Person.sql | 156 | | sqlserver-to-postgress-migration/postgress/procedures/usp_GetSalesOrdersByDateRange.sql | 153 | | adventureworks/procedures/usp_GetSalesOrdersByDateRange.sql | 142 | | sqlserver-to-postgress-migration/migration-app/sqlserver-to-postgress-migration.csproj | 138 | | sqlserver-to-postgress-migration/postgress/tables/Customer.sql | 135 | | adventureworks/tables/Person.sql | 127 | | sqlserver-to-postgress-migration/postgress/procedures/usp_UpdateProductListPrices.sql | 110 | | sqlserver-to-postgress-migration/postgress/procedures/usp_GetCustomersByTerritory.sql | 102 | | adventureworks/procedures/usp_GetCustomersByTerritory.sql | 91 | | adventureworks/tables/Customer.sql | 81 | | adventureworks/procedures/usp_UpdateProductListPrices.sql | 74 |
File Name | Action | Summary of Changes |
---|---|---|
.system/code/typescript/capabilities/devops/integrations/github/index.ts | CREATE | Created TypeScript implementation for GitHub DevOps integration |
.system/code/typescript/capabilities/devops/integrations/github/package.json | CREATE | Created package.json for GitHub DevOps integration |
.system/code/typescript/capabilities/devops/integrations/github/tsconfig.json | CREATE | Created tsconfig.json for GitHub DevOps integration |
.system/code/typescript/capabilities/devops/integrations/github/index.test.ts | CREATE | Created test file for GitHub DevOps integration |
.system/code/typescript/capabilities/devops/integrations/gitlab/index.ts | CREATE | Created TypeScript implementation for GitLab DevOps integration |
.system/code/typescript/capabilities/devops/integrations/gitlab/package.json | CREATE | Created package.json for GitLab DevOps integration |
.system/code/typescript/capabilities/devops/integrations/gitlab/tsconfig.json | CREATE | Created tsconfig.json for GitLab DevOps integration |
.system/code/typescript/capabilities/devops/integrations/gitlab/index.test.ts | CREATE | Created test file for GitLab DevOps integration |
File Name | Action | Summary of Changes |
---|---|---|
.system/code/typescript/capabilities/devops/integrations/azure-devops/package.json | CREATE | Created package.json for Azure DevOps integration |
.system/code/typescript/capabilities/devops/integrations/azure-devops/tsconfig.json | CREATE | Created tsconfig.json for Azure DevOps integration |
.system/code/typescript/capabilities/devops/integrations/azure-devops/index.test.ts | CREATE | Created test file for Azure DevOps integration |
.system/code/typescript/processes/create-project-and-repo/index.ts | CREATE | Created TypeScript implementation for create-project-and-repo process |
.system/code/typescript/processes/create-project-and-repo/package.json | CREATE | Created package.json for create-project-and-repo process |
.system/code/typescript/processes/create-project-and-repo/tsconfig.json | CREATE | Created tsconfig.json for create-project-and-repo process |
File Name | Action | Summary of Changes |
---|---|---|
.system/code/typescript/capabilities/devops/integrations/azure-devops/index.ts | CREATE | Created TypeScript implementation for Azure DevOps integration |
Programming Language
C#
Processing Instructions
Task Details
I'm going to show you capability models (OpenAPI specs) so you can understand what the Capability models are intended to do. I need you to implement the OpenAPI capability models in source code, against the implementation definitions found in the
.system/definitions/integrations
folder. Each integration definition contains a {integration-code}.md file with details on what capabilities the implementation should implement.Capability Implementation Code Generation
The generated code should be stored as
.system/code/{language-code}/capabilities/{capability-code}/integrations/{integration-code}/
in this naming pattern use:Each implementation should be compliable as it's own package, because it will later be composed via dependency injection when the individual implementations are combined into a platform deployment.
Process Code Generation
Processes should be implemented in the source code programming language specified. The source for the processes should be stored in this pattern
.system/code/{language-code}/processes/{process-code}
so each process will be in it's own location. You can read the description for a process in the.system/definitions/processes/
folder. Processes should try to use operations defined in the capaiblities implemented to implement their logic.Programming Language to Use
typescript
Source Branch
main