Граф коммитов

6 Коммитов

Автор SHA1 Сообщение Дата
Qiaoqiao Zhang 1fb6b2d250
multi-client-resolve-comments (#26602)
update multi-client and multi-endpoint design doc to resolve comments
2023-07-25 13:21:34 +08:00
Qiaoqiao Zhang a7c3acb80d
Design review for multi-client and multi-endpoint in modular (#26164)
In this design doc, we will mainly review how the multi-client libraries
and multi-endpoint libraries look like in our JS modular.
2023-07-25 11:12:22 +08:00
Jose Manuel Heredia Hidalgo 78bd1e78b5
Add customize to dev-tool (#25982) 2023-05-30 10:12:47 -07:00
Will Temple 232c15948a
[design/dev-tool] automated migration framework (#25044)
This pull request adds a design document for an automated migration
framework that, if accepted, will be integrated into `dev-tool`.

I've come to view a tool like this as required to support continued
incremental updates across the monorepo.

I won't describe the tool too much in this description, since it's
described in the included Markdown file, but it basically works like a
git merge:

- dev-tool tracks a list of migrations, `dev-tool migrate --list` will
show the ones that haven't been applied to a package.
- you "merge" the migrations into a package using `dev-tool migrate`.
Migrations can be fully or partially automatic _OR_ manual. The tool
will tell you what to do.
- if the migration fails, it is suspended and you have the chance to fix
it and then run `dev-tool migrate --continue` and it will re-check it,
or you can run `dev-tool migrate --abort` to cancel the process.
- if a migration succeeds, a commit is created for it in the current
branch and the next migration is run. Migrations are run in order
starting from the oldest.

This PR is a work in progress pending comments.
2023-05-03 12:04:04 -04:00
Matthew Podwysocki 07b9aed360
[dev tool] Add design docs for README snippets (#24537)
### Packages impacted by this PR

- [dev-tool]

### Issues associated with this PR


### Describe the problem that is addressed by this PR

Adds a design document on how we are going to do snippet extraction for
READMEs and source code.

### 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?


### Are there test cases added in this PR? _(If not, why?)_


### Provide a list of related PRs _(if any)_

- #24536

### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

### Checklists
- [ ] 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)

---------

Co-authored-by: Will Temple <witemple@microsoft.com>
2023-03-28 14:53:29 +00:00
Matthew Podwysocki db3a5752c1
[design] Adding modular design document (#24538)
### Packages impacted by this PR

- [@azure/notification-hubs]

### Issues associated with this PR


### Describe the problem that is addressed by this PR

Adds a design document for modular design for all projects, adding
subpath exports and extended ESM support

### 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?


### Are there test cases added in this PR? _(If not, why?)_


### Provide a list of related PRs _(if any)_


### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

### Checklists
- [ ] 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)
2023-02-16 02:54:42 +00:00