Validate @useAuth is unique on node (#2958)

fix #2787 having multiple has no effect, the latest value will override the previous ones so there is no reason to use `@useAuth` twice on the same node --------- Co-authored-by: Brian Terlson <brian.terlson@microsoft.com>
microsoft · Feb 28, 2024 · c9c1f3e · c9c1f3e
1 parent f884772
commit c9c1f3e
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/.chronus/changes/validate-useauth-unique-2024-1-27-17-26-52.md b/.chronus/changes/validate-useauth-unique-2024-1-27-17-26-52.md
@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: feature
+packages:
+  - "@typespec/http"
+---
+
+Validate that only one `@useAuth` decorator is applied to a type.
diff --git a/packages/http/src/decorators.ts b/packages/http/src/decorators.ts
@@ -436,6 +436,7 @@ export function $useAuth(
   entity: Namespace | Interface | Operation,
   authConfig: Model | Union | Tuple
 ) {
+  validateDecoratorUniqueOnNode(context, entity, $useAuth);
   const [auth, diagnostics] = extractAuthentication(context.program, authConfig);
   if (diagnostics.length > 0) context.program.reportDiagnostics(diagnostics);
   if (auth !== undefined) {