-
Notifications
You must be signed in to change notification settings - Fork 12
Closed
Labels
CLIPluginsGreenwood PluginsGreenwood PluginsRFCProposal and changes to workflows, architecture, APIs, etcProposal and changes to workflows, architecture, APIs, etcalpha.0breakingdocumentationGreenwood specific docsGreenwood specific docsfeatureNew feature or requestNew feature or requestv0.32.0
Milestone
Description
Summary
While Greenwood is a build tool without much of a public API other than its CLI and plugins, there are some areas that should probably provide typing to users through JSDocs, maybe TS but I'm not super keen on TypeScript in libraries.
Details
Most obvious ones that come to mind are:
- greenwood.config.js, even if just JS Docs style, ex.
/** @type {import('@greenwood/cli').GreenwoodConfig} */ export default { /* config options here */ }
- Plugins API (and get rid of that silly
ResourceInterface
lol) - Content as Data - like the data client
- others?
We would also want to make sure we validate these through CI somehow, ideally using these config files in our own projects and / or test cases.
Raised in #1292 (comment), a good point was raised about authoring Greenwood plugins (and probably also greenwood.config.js in TypeScript. Might need to make another issue for that once we can land this one first, unless its easy to do it all in one go with something like sucrase, which we are using now in WCC.
lschierer
Metadata
Metadata
Assignees
Labels
CLIPluginsGreenwood PluginsGreenwood PluginsRFCProposal and changes to workflows, architecture, APIs, etcProposal and changes to workflows, architecture, APIs, etcalpha.0breakingdocumentationGreenwood specific docsGreenwood specific docsfeatureNew feature or requestNew feature or requestv0.32.0
Type
Projects
Status
✅ Done