From 238391107fc15ccb4ec939cff8750c70956bd646 Mon Sep 17 00:00:00 2001 From: Steve Rice Date: Tue, 8 Oct 2024 11:59:34 -0700 Subject: [PATCH] Fix link to REST metadata emitter sample Samples were moved to `specs/` in 31fd5abf97f9c77919ed9fa10a147a8b6c2fed80 --- docs/extending-typespec/emitter-metadata-handling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extending-typespec/emitter-metadata-handling.md b/docs/extending-typespec/emitter-metadata-handling.md index 70493280e7..ca87eca6d3 100644 --- a/docs/extending-typespec/emitter-metadata-handling.md +++ b/docs/extending-typespec/emitter-metadata-handling.md @@ -15,7 +15,7 @@ When we say that emitters should handle things consistently, we mean they should If you're new to writing emitters, begin with the [emitter basics](./emitters-basics.md). -Next, examine the [REST metadata emitter sample](https://github.com/microsoft/typespec/tree/main/packages/samples/rest-metadata-emitter). This sample uses all of the APIs discussed below to create a simple textual representation. It intentionally avoids splitting types like the OpenAPI emitter to highlight that this is not mandatory. Instead, it includes contextual comments to indicate how data depends on context. +Next, examine the [REST metadata emitter sample](https://github.com/microsoft/typespec/tree/main/packages/samples/specs/rest-metadata-emitter). This sample uses all of the APIs discussed below to create a simple textual representation. It intentionally avoids splitting types like the OpenAPI emitter to highlight that this is not mandatory. Instead, it includes contextual comments to indicate how data depends on context. However, if you want your emitter to split types like OpenAPI, you can still use the same API. Cross-referencing with the official [OpenAPI emitter](../emitters/openapi3/openapi.md) where these APIs are called can also be helpful.