@azure-rest/agrifood-farming 1.0.0-alpha.20250108.1 → 1.0.0-alpha.20250109.1

package/README.md

@@ -53,13 +53,13 @@ AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET
 
 Use the returned token credential to authenticate the client:
 
-```typescript
-import FarmBeats from "@azure-rest/agrifood-farming";
+```ts snippet:CreateFarmBeatsClient
+import { FarmBeats } from "@azure-rest/agrifood-farming";
 import { DefaultAzureCredential } from "@azure/identity";
 
 const client = FarmBeats(
   "https://<farmbeats resource name>.farmbeats.azure.net",
-  new DefaultAzureCredential()
+  new DefaultAzureCredential(),
 );
 ```
 
@@ -95,17 +95,17 @@ Fam operations includes details pertaining to tilling, planting, application of
 Once you have authenticated and created the client object as shown in the [Authenticate the client](#create-and-authenticate-a-farmbeats-rest-client)
 section, you can create a party within the Data Manager for Agriculture resource like this:
 
-```typescript
-import FarmBeats, { isUnexpected } from "@azure-rest/agrifood-farming";
+```ts snippet:CreateParty
+import { FarmBeats, isUnexpected } from "@azure-rest/agrifood-farming";
 import { DefaultAzureCredential } from "@azure/identity";
 
 const client = FarmBeats(
   "https://<farmbeats resource name>.farmbeats.azure.net",
-  new DefaultAzureCredential()
+  new DefaultAzureCredential(),
 );
 
 const partyId = "test_party";
-const result = await farmbeatsClient.path("/parties/{partyId}", partyId).patch({
+const result = await client.path("/parties/{partyId}", partyId).patch({
   body: {
     name: "Contoso Party",
     description: "Your custom party description here",
@@ -126,22 +126,22 @@ console.log(`Created Party: ${party.name}`);
 
 ### List Parties
 
-```typescript
-import FarmBeats, { isUnexpected } from "@azure-rest/agrifood-farming";
+```ts snippet:ListParties
+import { FarmBeats, isUnexpected, paginate } from "@azure-rest/agrifood-farming";
 import { DefaultAzureCredential } from "@azure/identity";
 
 const client = FarmBeats(
   "https://<farmbeats resource name>.farmbeats.azure.net",
-  new DefaultAzureCredential()
+  new DefaultAzureCredential(),
 );
 
-const response = await farmbeatsClient.path("/parties").get();
+const response = await client.path("/parties").get();
 
 if (isUnexpected(response)) {
   throw response.body.error;
 }
 
-const parties = paginate(farmbeatsClient, response);
+const parties = paginate(client, response);
 
 // Log each party id
 for await (const party of parties) {
@@ -160,7 +160,7 @@ For additional samples, please refer to the [samples folder][samples_folder]
 
 Enabling logging may help uncover useful information about failures. In order to see a log of HTTP requests and responses, set the `AZURE_LOG_LEVEL` environment variable to `info`. Alternatively, logging can be enabled at runtime by calling `setLogLevel` in the `@azure/logger`:
 
-```javascript
+```ts snippet:SetLogLevel
 import { setLogLevel } from "@azure/logger";
 
 setLogLevel("info");

package/package.json

@@ -3,7 +3,7 @@
   "sdk-type": "client",
   "author": "Microsoft Corporation",
   "description": "An isomorphic REST client library for the Azure FarmBeats Service.",
-  "version": "1.0.0-alpha.20250108.1",
+  "version": "1.0.0-alpha.20250109.1",
   "keywords": [
     "node",
     "azure",
@@ -73,7 +73,7 @@
     "unit-test": "dev-tool run vendored cross-env TEST_MODE=playback && npm run unit-test:node && npm run unit-test:browser",
     "unit-test:browser": "npm run clean && dev-tool run build-package && dev-tool run build-test && dev-tool run test:vitest --browser",
     "unit-test:node": "dev-tool run test:vitest",
-    "update-snippets": "echo skipped"
+    "update-snippets": "dev-tool run update-snippets"
   },
   "sideEffects": false,
   "autoPublish": false,