Repository navigation
fix(attributes): Remove any as valid attribute type - #677
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. Bug Fixes 🐛
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d372b91. Configure here.
| "type": { | ||
| "description": "The type of the attribute value", | ||
| "enum": ["string", "boolean", "integer", "double", "string[]", "boolean[]", "integer[]", "double[]", "any"] | ||
| "enum": ["string", "boolean", "integer", "double", "string[]", "boolean[]", "integer[]", "double[]"] |
There was a problem hiding this comment.
Leftover any type branch
Low Severity
Removing any from the type enum leaves an unreachable oneOf branch that still matches const: "any". That branch can never validate now and is leftover from the previous iteration this change is cleaning up.
Reviewed by Cursor Bugbot for commit d372b91. Configure here.


#662 accidentally left
anyas a valid attribute type in the schema, which stems from a previous iteration of the PR. This cleans it up.