Convert the analyze-change.ps1 to typescript which allows to reuse a
common config for which area belong to who as well as some other
helpers.
The testing also is then all built-in the same system
This PR fixes the responses in operation not deserializing issue, but
uncovers another bug about how the convenience methods are implemented.
---------
Co-authored-by: m-nash <64171366+m-nash@users.noreply.github.com>
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to
3.0.3.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="74b2db2938"><code>74b2db2</code></a>
3.0.3</li>
<li><a
href="88f1429a0f"><code>88f1429</code></a>
update eslint. lint, fix unit tests.</li>
<li><a
href="415d660c30"><code>415d660</code></a>
Snyk js braces 6838727 (<a
href="https://redirect.github.com/micromatch/braces/issues/40">#40</a>)</li>
<li><a
href="190510f79d"><code>190510f</code></a>
fix tests, skip 1 test in test/braces.expand</li>
<li><a
href="716eb9f12d"><code>716eb9f</code></a>
readme bump</li>
<li><a
href="a5851e57f4"><code>a5851e5</code></a>
Merge pull request <a
href="https://redirect.github.com/micromatch/braces/issues/37">#37</a>
from coderaiser/fix/vulnerability</li>
<li><a
href="2092bd1fb1"><code>2092bd1</code></a>
feature: braces: add maxSymbols (<a
href="https://github.com/micromatch/braces/issues/">https://github.com/micromatch/braces/issues/</a>...</li>
<li><a
href="9f5b4cf473"><code>9f5b4cf</code></a>
fix: vulnerability (<a
href="https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727">https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727</a>)</li>
<li><a
href="98414f9f1f"><code>98414f9</code></a>
remove funding file</li>
<li><a
href="665ab5d561"><code>665ab5d</code></a>
update keepEscaping doc (<a
href="https://redirect.github.com/micromatch/braces/issues/27">#27</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/micromatch/braces/compare/3.0.2...3.0.3">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
You can trigger a rebase of this PR by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/microsoft/typespec/network/alerts).
</details>
> **Note**
> Automatic rebases have been disabled on this pull request as it has
been open for over 30 days.
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Contributes to https://github.com/microsoft/typespec/issues/3938
In `autorest.csharp` we do not have a `InputNamespace` converter - but
we have one here, and we are asserting the auth to never be null, but it
is not true, some project does not define their auth.
Fixes https://github.com/microsoft/typespec/issues/3813
- Adds tests for OutputLibraryVisitor
- Renames the Mocks folder to TestHelpers
- Adds protected ctors and unseals several types for mocking
- Visits constructors in OutLibraryVisitor
- Updates TypeProvider.Update to take IEnumerable instead of List
New pr from this branch as it had some weird docusaurus issue not
reproducable anywhere else and just changing branch fixes it somehow
https://github.com/microsoft/typespec/pull/3934
Notable:
- vitest: 2.x
- prettier update that does a minor formatting change by adding
parentheses in some ternary expression
Fixes regression introduced in #3908 where docs set at the union level
were being applied to each union variant.
Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>
Fixes#3811
Root cause seemed to be that when encountering 2+ non-null items in a
union, placeholders weren't getting wrapped by ObjectBuilder and thus
the emitter wasn't resolving circular references correctly.
Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>
Fixes https://github.com/microsoft/typespec/issues/3827
Also adds a Configure hook so that AddVisitor can be called directly
from the Plugin. Considered just using the ctor but that would mean we
would have virtual property calls in a ctor.
This PR seeks to update the emitter by adding the extensions defined on
a namespace to the root of the OpenApi document.
Fixes#3837
---------
Co-authored-by: Timothee Guerin <timothee.guerin@outlook.com>
Fixes#3646
Updated `scanDoc` to only update the escaped flag when a backslash
precedes `@`. This is the only character we currently unescape later on
in this scenario currently.
Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>
fix#3874 (Examples not working with nested model in array)
fix#3872 (Examples not working when type is union)
Additionally found the following issues that this fix:
- not working when type was `unknown`
- not working with `Record`
Switch to release MCG to public feed.
Current MCG emitter is published into a internal feed. Now MCG will be
used as plugin in autorest.csharp emitter, MCG emitter needed to be
installed when run autorest.csharp emitter, so we need to publish MCG to
a public feed.
Fix https://github.com/microsoft/typespec/issues/3861
Move `readme.md` to package top-level directory so that readme can show
in npm.
Contributes to https://github.com/microsoft/typespec/issues/3825
Change CatchExpression to be CatchStatement since it is really a
statement.
Make each of Try/Catch/Finally statements implement
`IEnumerable<MethodBodyStatement>`. This is consistent with
IfStatement/ForStatement,etc and it allows for writing generator code
with structure that mirrors what the generated code will look like
(apart from having comma delimiters as opposed to semicolons) e.g.
```c#
new TryStatement
{
statement1,
statement2
}
```
Generates
```c#
try
{
...
...
}
```
When I run the test cases in the other PR, I happened to notice that
these tests are disabled.
Since we already get those ApiTypes refactored for a few weeks, we
should reenable them.
This came up when testing out the plugin extensibility where a visitor
would write out a method body statement. The code declaration would be
declared twice - once when actually writing the library, and the second
time when writing the method body statement from the visitor.
Timothee Guerin
Dapeng Zhang
JoshLove-msft
m-nash
dependabot[bot]
Christopher Radek
Jorge Rangel
Greg Poirier
Rodge Fu
ShivangiReja
Sarangan Rajamanickam
Maggie Kimani
Pan Shao
Crystal YU
Mario Guerra