- add dep to `uglify-js` in dev-tool
- rush update
- replace "uglifyjs" with "dev-tool run vendored yglifyjs"
- remove dependency to "uglifyjs" in sdk packages
***NO_CI***
- apply lint:fix results
- revert fixes that are not related to consistent-type-imports and cases error
- regenerate .api.md files
- format
- update core-comparison diff
also remove dependency on `@microsoft/api-extractor` as we already move to
`dev-tool run extract-api` which calls api-extractor Api instead.
***NO_CI***
***NO_CI***
- replace version to "~5.6.2"
- rush update
- add `"skipLibCheck": true` for several packages that are affected by https://github.com/vitest-dev/vitest/issues/4688
- [formrecognizer] help TypeScript to understand with more explicit type
- [schema-registry-{avro,json}] skip lib check due to lru-cache issue with the Iterator TReturn change
https://github.com/isaacs/node-lru-cache/issues/348
- [eslint-plugin] github-source-headers rule should use "MIT License".
This change updates our linter rule and the whole repository to have consistent
license header.
***NO_CI***
- remove "All rights reserved." from header
- "MIT license" => "MIT License"
Previously dev-tool has been fixed to generate correct include path in samples
tsconfig.json but samples were not updated.
This PR fixes the samples tsconfig.json in one run; otherwise with the recent
branch protection policy changes, when individual packages re-publish samples,
js-core team would have to approve the tsconfig.json changes.
***NO_CI***
There's some behavior change that adds parentheses for nullish coalescing in
ternary. So we will need to re-format our code base.
- remove prettier from packages that don't need them since we run the vendored
version via dev-tool
which only extends from tsconfig.json. There might be more customization for
packages in the early days but not any more.
This PR removes it and updates packages to extends tsconfig.json directly
***NO_CI***
Update tsp-location.yaml to point to a commit from main in the spec repo
and regenerate. The previous commit hash was from a branch never merged,
blocking the attempt to release the sdk
After regenerating from latest tsp main, those were the changes
introduced:
* EnvionmentType name was updated to readonly (later fix added on the
typespec)
* PollingHelper and lro packages got updated (updated by code gen). Live
test for the LRO operations was executed and no issue was detected.
Previous PR for current sdk:
https://github.com/Azure/azure-sdk-for-js/pull/29512
APIView: [@azure-rest/developer-devcenter -
apiview.dev](https://apiview.dev/Assemblies/Review/e17096012eb7466a8aab7c74742c6bff?revisionId=b4d2f5f84d98499dacfcc5e7cdd15d52)
---------
Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
Run `rush build` on the repo to ensure the newly added `source` fields
are generated.
This avoids unnecessary noise on PRs that may build tshy packages as
part of their dependency graph (such as #29374)
as packages using tshy has been migrated to ESM and these rules no
longer apply to them.
This PR skip these rules to avoid having to turn them off for individual
packages.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
We could remove these rules too. Although it's still nice to have them
before we migrage all packages to ESM with tshy.
To do:
[x] Regenerate from merged tsp spec
[x] Update tests to use vitest
[x] Record tests
[x] Update samples
[] ~~Update Readme~~
[x] Update Changelog
[x] Update LRO status model fixed in tsp latest api version pr
---------
Co-authored-by: Lei Tian <leti@microsoft.com>
This change migrates every package to the latest major version of
identity in order to ensure we can catch any regressions earlier in the
development process.
I chose to upgrade the samples' package.json as well - but happy to
revert that if there are objections.
***NO_CI***
Our tests use the type `Mocha.Context` when they need to pass the test context
to test recorder. However, without a dev dependency on `@types/mocha`
compilation may fail when recorder constructor is changed from taking a
`Mocha.Test` to taking an interface that is compatible.
This change ensures the dev depedency on `@types/mocha` too if there's a dev
dependency on `mocha`.
***NO_CI***
***NO_CI***
Latest versions of prettier now correctly formats `tsconfig.json`, which results
in differences with previous version of 3.1.1 in pnpm-lock.yaml. This is failing
the automated rush update pipeline because `check-format` fails with version
3.2.4.
This includes changes of
- bumping prettier version to ^3.2.4
- running `rush format`
***NO_CI***
- remove dev dependency `prettier` from non-tool packages when possible and
update them to run vendored prettier for `check-format` and `format` scripts
- upgrade rest of packages to prettier v3
- run `rush format` for all rush packages
This is a follow-up to https://github.com/Azure/azure-sdk-for-js/pull/28127 to
move the rest of repo to prettier v3.
# Description
For js, we had a previous
[PR](https://github.com/Azure/azure-sdk-for-js/pull/25859) which was
mainly to address changes caused by updating the DevCenter Data Plane
API to 2023-04-01 version. Since the PR was not completed, I have picked
the commits from there with the intention of reusing tests and samples.
On top of that, I have regenerated the SDK from TypeSpec since this is
the new type of generation desired going forward.
This will be released as a beta SDK and later down the road we will be
working on the stable SDK for this same API version. The recordings were
updated to the [assets
repo](https://github.com/Azure/azure-sdk-assets/tree/js/devcenter/developer-devcenter-rest_89c2b6dafe).
The changes to add typespec support can be find at
[feature/devcenter-tsp](https://github.com/Azure/azure-rest-api-specs/pull/26359).
Note the PR hasn't been merged, so we will have a separate pr in the
future to update the commit hash pointing to the new tsp location.
# All SDK Contribution checklist:
- [ ] **The pull request does not introduce [breaking changes]**
- [x] **CHANGELOG is updated for new features, bug fixes or other
significant changes.**
- [x] **I have read the [contribution
guidelines](https://github.com/Azure/azure-sdk-for-python/blob/main/CONTRIBUTING.md).**
## General Guidelines and Best Practices
- [x] Title of the pull request is clear and informative.
- [x] There are a small number of commits, each of which have an
informative message. This means that previously merged commits do not
appear in the history of the PR. For more information on cleaning up the
commits in your PR, [see this
page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md).
### [Testing
Guidelines](https://github.com/Azure/azure-sdk-for-python/blob/main/CONTRIBUTING.md##building-and-testing)
- [x] Pull request includes test coverage for the included changes.
### Pipeline runs
Dry runs on the release pipeline:
https://dev.azure.com/azure-sdk/internal/_build?definitionId=5622&_a=summary
### List of tests
(same as previous PR)
DevBox
- [x] get_pool
- [x] list_pools
- [x] get_dev_box
- [x] get_remote_connection
- [x] get_action
- [x] list_actions
- [x] skip_action
- [x] delay_action
- [x] delay_all_actions
- [x] get_schedule
- [x] list_schedules
- [x] list_dev_boxes
- [x] list_all_dev_boxes
- [x] list_all_dev_boxes_by_user
- [x] begin_create_dev_box
- [x] begin_delete_dev_box
- [x] begin_start_dev_box
- [x] begin_stop_dev_box
- [x] begin_restart_dev_box
DevCenter
- [x] get_project
- [x] list_projects
Environments
- [x] begin_delete_environment
- [x] begin_create_or_update_environment
- [x] list_environment_types
- [x] list_catalogs
- [x] list_environments
- [x] list_all_environments
- [x] get_environment_definition
- [x] list_environment_definitions
- [x] list_environment_definitions_by_catalog
- [x] get_catalog
- [x] get_environment
Also updated samples.
---------
Co-authored-by: Sean Brennan <sebrenna@microsoft.com>
Co-authored-by: Oleg Demchenko <oldemche@microsoft.com>
Some files are not formated in commits that were merged without CI. This
PR updates them with the result from `rush format`, and also fixes
`format` script for ts-http-runtime
Jeremy Meng
Matthew Podwysocki
Maor Leger
Jeremy Meng
Deyaaeldeen Almahallawi
ZiWei Chen
Azure SDK Bot
Driele Neves Ribeiro
Maor Leger