Skip to content

Conversation

@MattDevy
Copy link
Contributor

As per #5642 adds checks for variant types allowed in specific cases

@MattDevy MattDevy requested a review from margaretjgu November 14, 2025 16:23
@MattDevy MattDevy added skip-backport This pull request should not be backported spec validation and removed specification labels Nov 14, 2025
@github-actions
Copy link
Contributor

Following you can find the validation changes against the target branch for the APIs.

No changes detected.

You can validate these APIs yourself by using the make validate target.

| `invalid-node-types` | The spec uses a subset of TypeScript, so some types, clauses and expressions are not allowed. |
| `no-generic-number` | Generic `number` type is not allowed outside of `_types/Numeric.ts`. Use concrete numeric types like `integer`, `long`, `float`, `double`, etc. |
| `request-must-have-urls` | All Request interfaces extending `RequestBase` must have a `urls` property defining their endpoint paths and HTTP methods. |
| `no-variants-on-responses` | `@variants` is only supported on Interface types, not on Request or Response classes. Use value_body pattern with `@codegen_name` instead. |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! Although I think it would be nice to extend off of the existing variant rule...at least thats what I had in mind

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would make a lot of sense. I will refactor it into the existing rule Monday morning! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-backport This pull request should not be backported spec validation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants