microsoft
Release of `tspd` package
Describe the bug
As of writing this issue, the latest version tag for @typespec/compiler is currently 0.56.0, which was published 14 hours ago. However, the latest version tag for @typespec/tspd is currently 0.47.0-dev.0, which was published 3 months ago.
This is causing an issue because I was trying to use the gen-extern-signatures command but that was first added 2 months ago and is not present in the latest published version. As a side node, there are also some required dependencies only being listed in devDependencies that should either be moved to dependencies or listed as peerDependencies (typedoc and typedoc-plugin-markdown).
Reproduction
NA
Checklist
- [X] Follow our Code of Conduct
- [X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
- [X] The provided reproduction is a minimal reproducible example of the bug.
Hi @smbecker this is by design(The original release was more of a failure in our pipeline) as the package is not very stable for now, specially the decorator signature generation. After the merge of the value PR https://github.com/microsoft/typespec/pull/3022 there is a decent amount of work to add to tspd to support object and array values nicely but I think after that we could consider releasing it and collecting feedback.
And good point about the depencencies issues, we'll have to fix that before the release
Bummer but thanks for the response @timotheeguerin. I was trying to do something similar to @typespec/protobuf but for graphql schemas and ran into the missing command. Obviously, that library can leverage it since it is part of the workspace but unfortunately, I can't. I'll keep an eye on this issue for if/when it ever gets released. In the meantime, I'll just work-around it.
This fell of the radar a little bit, we are releasing it as an experimental libraries. Explicit opt-in flags needed for all commands. The decorator signature generation is I think in a good state and should be move out of experimental in a not too long timeline The doc generation needs significant rework (specially around js generation) so this will stay experiemntal for the forceable future