Person

Pascal Wasem

GitHub@pwasemWebsitegithub.comlast push

Capabilities1

Provides 1
TypeScript patternsCAPTypeScript patternscapabilityHow an application is arranged once it is written in TypeScript — where handlers live, what registers them, and how business logic is kept apart from persistence. Distinct from typing, which is about the model being visible to the compiler; this is about the shape of the code around it.

Entries1

Group by
EntrySignals
Maintains1
cds-plugin-typescriptv0.1.8
none

CDS build task compiling TypeScript sources during cds build

Details

History4
  • cds-plugin-typescriptprovides[typescript-patterns] → what_it_doesThe edge carried no sentence. It now says what the plugin does at build time and that it says nothing about the arrangement of the code it compiles. Whether the edge belongs on typescript-patterns is an open editorial question recorded with the capability's review: capire now ships a cds build task for TypeScript in @cap-js/cds-typer, which puts this plugin beside the core's toolchain answer rather than beside the arrangement options. No facet values are stated, because the capability's four facets ask about the arrangement and the README answers none of them.
  • cds-plugin-typescriptartifact_type → build-toolTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
  • cds-plugin-typescriptdescription.one_line → A CDS build task that compiles TypeScript sources during `cds build`, so the deployed artefact is JavaScript without a separate build step in the pipeline.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
  • First entry seenDiscovered via npm registry, The discovery pass.
Profile1
For your agent