@azure-tools/typespec-azure-core 0.28.0 → 0.29.0-dev.1

package/README.md

@@ -114,13 +114,13 @@ This marks the `Contoso.WidgetManager` namespace as a service namespace in this
 
 ### Using the versioned Azure.Core types
 
-Before you can use the models and operations defined in the `Azure.Core` namespace, you will need to specify the API version of the `Azure.Core` library that your service uses. You can do this by adding the `@versionedDependency` decorator to the `Contoso.WidgetManager` namespace as seen here:
+Before you can use the models and operations defined in the `Azure.Core` namespace, you will need to specify the API version of the `Azure.Core` library that your service uses. You can do this by adding the `@useDependency` decorator to the `Contoso.WidgetManager` namespace as seen here:
 
 ```typespec
 @service({
   title: "Contoso Widget Manager",
 })
-@versionedDependency(Azure.Core.Versions.v1_0_Preview_2)
+@useDependency(Azure.Core.Versions.v1_0_Preview_2)
 namespace Contoso.WidgetManager;
 ```
 
@@ -364,12 +364,10 @@ Here is an example for the `WidgetManager` service:
   title: "Contoso Widget Manager",
 })
 @versioned(Contoso.WidgetManager.Versions)
-@versionedDependency(
-  [[Contoso.WidgetManager.Versions.v2022_08_31, Azure.Core.Versions.v1_0_Preview_2]]
-)
 namespace Contoso.WidgetManager;
 
 enum Versions {
+  @useDependency(Azure.Core.Versions.v1_0_Preview_1)
   v2022_08_31: "2022-08-31",
 }
 ```
@@ -378,26 +376,28 @@ There are a few things to point out here:
 
 - We define an `enum` called `Versions` inside of the service namespace. For each service version, we map a version symbol like `v2022_08_31` to a version string like `2022-08-31`. This service currently only has a single version, but we can add more to this enum as things change over time.
 - We add the `@versioned` decorator and reference the `Versions` enum we defined using the fully-qualified name `Contoso.WidgetManager.Versions`. This marks the service as being versioned and specifies the set of versions.
-- We change the `@versionedDependency` decorator we used previously to now link each service version to a specific version of `Azure.Core`. See the [Using Azure.Core Versions](#using-azurecore-versions) section for more information.
+- We change the `@useDependency` decorator we used previously to now link each service version to a specific version of `Azure.Core`. See the [Using Azure.Core Versions](#using-azurecore-versions) section for more information.
 
 Imagine that it's 3 months later and you want to release a new version of your service with some slight changes. Add a new version to the `Versions` enum:
 
 ```typespec
 enum Versions {
+  @useDependency(Azure.Core.Versions.v1_0_Preview_1)
   v2022_08_31: "2022-08-31",
   v2022_11_30: "2022-11-30",
 }
 ```
 
-You will also need to change the `@versionedDependency` decorator:
+You will also need to add the `@useDependency` decorator:
 
 ```typespec
-@versionedDependency(
-  [
-    [Contoso.WidgetManager.Versions.v2022_08_31, Azure.Core.Versions.v1_0_Preview_2],
-    [Contoso.WidgetManager.Versions.v2022_11_30, Azure.Core.Versions.v1_0_Preview_2]
-  ]
-)
+enum Versions {
+  @useDependency(Azure.Core.Versions.v1_0_Preview_1)
+  v2022_08_31: "2022-08-31",
+
+  @useDependency(Azure.Core.Versions.v1_0_Preview_2)
+  v2022_11_30: "2022-11-30",
+}
 ```
 
 Finally, you can express changes to your service using the `@added` and `@removed` decorators. Here's an example of adding a new property to `Widget` and removing an old one:
@@ -425,15 +425,15 @@ You can do a lot more with versioning decorators, so consult the `typespec-versi
 
 ### Using Azure.Core versions
 
-`typespec-azure-core` is a versioned TypeSpec library. This means that even as the TypeSpec portions of the typespec-azure-core library are updated, you can anchor each version of your spec to a [specific `Azure.Core` version](#library-versions). This is done by decorating your service namespace with the `@versionedDependency` decorator from the `typespec-versioning` library.
+`typespec-azure-core` is a versioned TypeSpec library. This means that even as the TypeSpec portions of the typespec-azure-core library are updated, you can anchor each version of your spec to a [specific `Azure.Core` version](#library-versions). This is done by decorating your service namespace with the `@useDependency` decorator from the `typespec-versioning` library.
 
-Simple TypeSpec specs need only pass the desired `Azure.Core` version into the `@versionedDependency` decorator:
+Simple TypeSpec specs need only pass the desired `Azure.Core` version into the `@useDependency` decorator:
 
 ```typespec
 @service({
   title: "Contoso Widget Manager",
 })
-@versionedDependency(Azure.Core.Versions.v1_0_Preview_2)
+@useDependency(Azure.Core.Versions.v1_0_Preview_2)
 namespace Contoso.WidgetManager;
 ```
 
@@ -444,13 +444,15 @@ If your spec has [multiple versions](#versioning-your-service), you will need to
   title: "Contoso Widget Manager",
 })
 @versioned(Contoso.WidgetManager.Versions)
-@versionedDependency(
-  [
-    [Contoso.WidgetManager.Versions.v2022_08_31, Azure.Core.Versions.v1_0_Preview_2],
-    [Contoso.WidgetManager.Versions.v2022_11_30, Azure.Core.Versions.v1_0_Preview_2]
-  ]
-)
 namespace Contoso.WidgetManager;
+
+enum Versions {
+  @useDependency(Azure.Core.Versions.v1_0_Preview_1)
+  v2022_08_31: "v20220831",
+
+  @useDependency(Azure.Core.Versions.v1_0_Preview_2)
+  v2022_11_30: "v20221130",
+}
 ```
 
 ## Advanced Topics
@@ -493,13 +495,14 @@ The operations defined against this singleton resource will also exclude the key
 
 ## Library Versions
 
-This is a versioned TypeSpec library which means that you must add the `@versionedDependency` decorator to your service namespace when you use its contents.
+This is a versioned TypeSpec library which means that you must add the `@useDependency` decorator to your service namespace when you use its contents.
 
 Here are the current versions:
 
+- `Azure.Core.Versions.v1_0_Preview_1`
 - `Azure.Core.Versions.v1_0_Preview_2`
 
-See the [Using Azure.Core Versions](#using-azurecore-versions) section for more details on how to use the `@versionedDependency` decorator.
+See the [Using Azure.Core Versions](#using-azurecore-versions) section for more details on how to use the `@useDependency` decorator.
 
 ## Library Tour
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@azure-tools/typespec-azure-core",
-  "version": "0.28.0",
+  "version": "0.29.0-dev.1",
   "author": "Microsoft Corporation",
   "description": "TypeSpec Azure Core library",
   "homepage": "https://azure.github.io/typespec-azure",
@@ -42,21 +42,21 @@
     "!dist/test/**"
   ],
   "peerDependencies": {
-    "@typespec/compiler": "~0.42.0",
-    "@typespec/http": "~0.42.0",
-    "@typespec/rest": "~0.42.0"
+    "@typespec/compiler": ">=0.42.0",
+    "@typespec/http": ">=0.42.0",
+    "@typespec/rest": ">=0.42.0"
   },
   "dependencies": {
-    "@typespec/lint": "~0.42.0"
+    "@typespec/lint": ">=0.42.0"
   },
   "devDependencies": {
-    "@typespec/compiler": "~0.42.0",
-    "@typespec/http": "~0.42.0",
-    "@typespec/rest": "~0.42.0",
-    "@typespec/eslint-config-typespec": "~0.6.0",
-    "@typespec/library-linter": "~0.42.0",
-    "@typespec/eslint-plugin": "~0.42.0",
-    "@typespec/versioning": "~0.42.0",
+    "@typespec/compiler": ">=0.42.0",
+    "@typespec/http": ">=0.42.0",
+    "@typespec/rest": ">=0.42.0",
+    "@typespec/eslint-config-typespec": ">=0.6.0",
+    "@typespec/library-linter": ">=0.42.0",
+    "@typespec/eslint-plugin": ">=0.42.0",
+    "@typespec/versioning": ">=0.42.0",
     "@types/mocha": "~10.0.0",
     "@types/node": "~18.11.9",
     "eslint": "^8.12.0",