Skip to content

[RFC]: refactor namespace TypeScript declaration automation #50

@kgryte

Description

@kgryte

Currently, our namespace TypeScript declaration workflow creates a single PR which includes changes to one or more namespaces. E.g., see stdlib-js/stdlib@87abb74.

The problem with this approach is that, depending on the changes, some namespaces may only have docs changes, while others may have feature additions, and yet others may have breaking changes. However, when we go to merge a namespace TypeScript declaration PR, we are forced to commit according to the semver of the most significant change. This is not ideal.

Instead, it would be best if each namespace was opened as a separate PR. In the commit referenced above, that would have been 2 PRs, one for each namespace. We could then make one a feat: commit and the other a docs: commit and the changelog for both namespaces would be appropriately scoped and automatic versioning would function as expected.

Time estimate with AI: 30min
Time estimate without AI: 45min

Prior Task Exposure: 4
External Resource Needs: 3

Metadata

Metadata

Assignees

Labels

EnhancementTask to enhance existing functionality.RefactorTask to refactor existing code.difficulty: 1Low degree of difficulty. Should be straightforward to implement and/or resolve.estimate: <2hrsTask which should take less than 2 hours.🤖 AIAllowed to use AI.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions