Skip to content

Commit

Permalink
Update links (Azure#22254)
Browse files Browse the repository at this point in the history
  • Loading branch information
MaryGao authored Jun 15, 2022
1 parent 782817c commit 2ac576e
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions documentation/RLC-quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,9 @@ We are working on to automatically generate everything right now, but currently

# How to write test for RLC

In order to release it, we need to add some tests for it to make sure we are delivering high quality packages. but before we add the test, we need to add a generate-test: true make the code generator generate the necessary change in package.json and tsconfig.json so that test framework can work. Once the generation finished, you will see a sampleTest.spec.ts file in your `{PROJECT_ROOT}/test/public` folder, which only has a empty test and you may change them into test against your own services.
In order to release it, we need to add some tests for it to make sure we are delivering high quality packages. but before we add the test, we need to add a `generate-test: true` make the code generator generate the necessary change in `package.json` and `tsconfig.json` so that test framework can work. Once the generation finished, you will see a `sampleTest.spec.ts` file in your `{PROJECT_ROOT}/test/public` folder, which only has a empty test and you may change them into test against your own services.

See the [Javascript Codegen Quick Start for Test](https://github.com/Azure/azure-sdk-for-js/blob/main/documentation/test-quickstart.md) for information on how to write and run tests for the Javascript SDK.

## Prerequisites

Expand Down Expand Up @@ -226,4 +228,9 @@ Please change the paths.include value as your own project path, and change the A
If there's already a ci.yml file in your project path. then the only thing you need to do is to add the Artifacts name and safeName of yours into that ci.yml.
# Create API View
You may also want to create API View when submitting a PR. You can do it easily by uploading a json file to [API View Website](https://apiview.dev/). The json file is under `<you-sdk-folder>/temp`, and its name ends with `api.json`. For example: `sdk/compute/arm-compute/temp/arm-compute.api.json`.
You may also want to create API View when submitting a PR. You can do it easily by uploading a json file to [API View Website](https://apiview.dev/). The json file is under `<you-sdk-folder>/temp`, and its name ends with `api.json`. For example: `sdk/compute/arm-compute/temp/arm-compute.api.json`.
# How to do customizations
There is many information about the SDK that AutoRest will never know, so you may want to do your customizations based on generated code.
We collect some common customization cases and you can read [Customization on the RLC rest-level client libraries](https://github.com/Azure/azure-sdk-for-js/blob/main/documentation/RLC-customization.md) for more details.

0 comments on commit 2ac576e

Please sign in to comment.