Meta-data source (manifest)

[Bartvds]

DT repository needs a meta-data source to provide more information about the definitions to be consumed by both internal and external tooling.

The likely candidate is to put manifest files with some JSON content in the definitions folders and have the tooling filter them out.

This Issue tracks the discussion & progress.

Proposals & prose:

• Organisation Doc: 02
• proposals

Some earlier discussions:

• Only run impacted tests for Pull Requests #1314
• Can these declaration files be separated and enabled for Bower? #428
• Re-evaluate the logic used to increment nuspec version  NugetAutomation#4

[Bartvds]

@staxmanade have you had chance to look at this? document 03

I'm now going to do a sweep to fix headers: #1570

Later I might use my parser (TSD has it) to start generating some json for these manifests.

A problem is still how to name these manifest files:

jquery.d.ts
jquery-test.ts

jquery.d.json
jquery.d.meta.json
jquery-meta.json
jquery.dt-meta.json
jquery.dt-manifest.json

[staxmanade]

The minimal and human parts of the manifest look good for now.

I proposed another name jquery.manifest as an example.

Let's start putting the manifest in an actual project (say jquery and a jquery plugin) to see how it looks?

[jakebailey]

Trying to do some issue cleanup; after converting to pnpm, all info is now in package.json.