- 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***
### Packages impacted by this PR
@azure/event-hubs
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/31067
### Describe the problem that is addressed by this PR
This PR adds runtime validation to the input message structure. This is
needed so that strict receivers that follow the AMQP spec don't reject
non-compliant messages.
### 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?
N/A
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
https://github.com/Azure/azure-sdk-for-js/pull/31330
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
***NO_CI***
Currently the rule only handles the case of
```ts
clientMethod(options: MethodOptions) {}
```
but not when the options bag parameter has a default value
```ts
clientMethod(options: MethodOptions = {}) {}
```
This change adds code to handle the latter.
- Add two unit tests
- Update the affected packages to suppress this rule as a warning
- react to the fix
***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"
Moving to a modular bicep definition so that we can share bits and
pieces between all of them. This PR factors out the key vault definition
so other bicep scripts can import it too. For now, it lives next to the
event hub's test-resources.bicep script but I'll consider moving it to a
central place once other libraries move to import it.
The PR also edits the script to make it more compact.
Live tests run:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4079360&view=results
***NO_CI***
- bump typescript-eslint dependencies version to ~8.2.0
- [eslint-plugin] suppress new linting errors appearing with v8
- [eslint-plugin] react to removed typescript-eslint property
related PR https://github.com/typescript-eslint/typescript-eslint/pull/9025
- [eslint-plugin] turn off @typescript-eslint/no-unused-expressions
as no-unused-expressions is already reported by eslint
- [dev-tool] fix new linting errors
- Remove @typescript-eslint/ban-types that no longer exists
and replace with more specific rules wherever applicable.
- [cosmosdb] combine the test eslint config with the main one
- delete catch expression when caught error is not used
- fix or suppress linting errors in code files
- replace .eslintrc.json with eslint.config.mjs
- fix linting errors
- URL is in global scope on all of our supported platforms
- we use "buffer" npm package for browsers support so suppressing errors
- add a config in eslint-plugin-azure-sdk for linting with type
information
- remove .eslint* and replace with eslint.config.mjs
- remove --ext from linting NPM scripts
- fix linting error: URL is now available in global scope on our
supported platforms.
***NO_CI***
- add one flat config file for perf tests
- update NPM scripts of these packages to use that flat config for perf tests
As eslint v8 still not switched to flat config by default, this change
temporarily uses `cross-env` to set `ESLINT_USE_FLAT_CONFIG=true`
Once we moved to eslint v9 the env var can be removed.
### Packages impacted by this PR
@azure/eventhubs-checkpointstore-blob
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
- migrates to use TSHY and vitest
- uses storage endpoint instead of storage connection string in the
tests
- enables browser testing
- updates test-resources.json accordingly
- fixes a behavior where an error is being wrapped in another
Live tests run:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4018408&view=results
### 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?
N/A
### Are there test cases added in this PR? _(If not, why?)_
N/A
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
- upgrade for app-configuration
- upgrade for ai-language-conversations
- upgrade for container-registry
- upgrade for event hubs checkpoint stores
- upgrade for mock-hub
The verbose reporter writes out the status of each unit test after it
gets executed. This is inline with our experience with mocha before and
it helps us track progress better in real time.
### Packages impacted by this PR
@azure/event-hubs
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
This PR does the following:
- migrates Event Hubs client library to the new world of using TSHY for
building the library and using vitest as the test runner
- consolidates client building in a single module and uses fully
qualified name spaces and token credentials to build clients instead of
using connection strings
- runs mock-hub once instead of in every test module
- disables min/max testing and samples testing because they're not
playing well with TSHY and vitest at the moment. I'll open an issue to
track turning them back on once the testing pipelines have been
upgraded.
Live Tests are passing:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4000037&view=results
### 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?
N/A
### Are there test cases added in this PR? _(If not, why?)_
N/A
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
This doesn't cover the many files still using secret sub configs with
custom principals, those will be migrated separately. This changes the
defaults to use file-based sub configs and service connections
everywhere else. It is intended to be merged after/alongside federated
auth mode becoming the default.
Relies on https://github.com/Azure/azure-sdk-tools/pull/8680
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***
Jeremy Meng
Deyaaeldeen Almahallawi
Wes Haggard
Jeremy Meng
Matthew Podwysocki
Maor Leger
ZiWei Chen
Ben Broderick Phillips