Azure / Azure/typespec-azure

Need a mechanism for targeting suppressions at groups of types

Open
#3,319 1 comment 0 reactions 0 assignees View on GitHub
design:needed eng
Dominant language
TypeScript
Stars
27
Forks
90
Avg merge
1d 22h
Merged PRs (30d)
156

Description

In the AIP scenario, The types from the OAI spec are brought into the AIP spec, transformations are added, and new APIs in a new namespace are added - some linting rules *should* apply to the new APIs, but should be suppressed in the core OAI types.

Some options for allowing this:
- Allow suppressions on a namespace impacted all contained types
- Allow suppressions on a per file or directory basis
- Create / provide guidance for creating a tool to add point suppressions to a spec

Contributor guide

Open the contributing guide

Research direction

Start by examining the AIP scenario described in the issue and how linting rules currently distinguish imported OAI types from new APIs. Compare namespace, file or directory, and generated point-suppression approaches. Done means a documented, agreed mechanism or guidance for targeting suppressions at groups of types.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.