Skip to content

Add maxLength constraints to useCases name and description fields#137

Merged
lindazqli merged 2 commits intomainfrom
copilot/add-field-length-limitations
Mar 6, 2026
Merged

Add maxLength constraints to useCases name and description fields#137
lindazqli merged 2 commits intomainfrom
copilot/add-field-length-limitations

Conversation

Copy link
Contributor

Copilot AI commented Mar 6, 2026

The useCases items in the server schema had no length limits on name or description, allowing unbounded input.

Schema changes

  • partners/server-schema.json: Added maxLength: 500 to useCases[].name and maxLength: 1000 to useCases[].description
"useCases": {
  "items": {
    "properties": {
      "name":        { "type": "string", "maxLength": 500, ... },
      "description": { "type": "string", "maxLength": 1000, ... }
    }
  }
}

Data fix

  • partners/servers/azure-mcp-server.json: Trimmed an existing use case description from 1036 → 997 characters to comply with the new limit, removing , Azure Managed Lustre and , Cloud Architect from the inline services enumeration.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: rkolesnikovDX <14820428+rkolesnikovDX@users.noreply.github.com>
Copilot AI changed the title [WIP] Add limitation to use case fields length Add maxLength constraints to useCases name and description fields Mar 6, 2026
@rkolesnikovDX rkolesnikovDX marked this pull request as ready for review March 6, 2026 17:29
@lindazqli lindazqli merged commit 067ae67 into main Mar 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants