Skip to content

Conversation

@melbourne2991
Copy link
Contributor

This does a couple of things:

  • More ergonomic
  • Know when a specific type request has completed. (Current finish event is insufficient, doesn't tell you which request is completed and is never called if the provided source code has no imports).

This does a couple of things:

- More ergonomic
- Know when a specific type request has completed. (Current finish event is insufficient, doesn't tell you which request is completed and is never called if the provided source code has no imports).
@orta
Copy link
Contributor

orta commented Jan 25, 2023

Seems reasonable to me, I'd recommend also bumping the package json version so when the PR is merged it will also release 👍🏻

@melbourne2991
Copy link
Contributor Author

@microsoft-github-policy-service agree

@melbourne2991
Copy link
Contributor Author

Seems reasonable to me, I'd recommend also bumping the package json version so when the PR is merged it will also release 👍🏻

Done 👍

@jakebailey jakebailey closed this May 18, 2023
@jakebailey jakebailey reopened this May 18, 2023
Copy link
Member

@jakebailey jakebailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but will merge/release this with the other PRs that require package publishes.

@jakebailey jakebailey mentioned this pull request Jul 25, 2023
4 tasks
@jakebailey
Copy link
Member

With bump versions with #2904 to minimize the waiting within the current infrastructure.

@jakebailey jakebailey enabled auto-merge (squash) July 25, 2023 21:03
@jakebailey jakebailey merged commit f2f7a04 into microsoft:v2 Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants