-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(nx-plugin): Update executor generator #16982
feat(nx-plugin): Update executor generator #16982
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
5ddc241
to
e9acd21
Compare
Looking at the errors does it make sense to create export type PromiseExecutor = ...
export type AsyncIterableIteratorExecutor = ...
export type Executor = PromiseExecutor | AsyncIterableIteratorExecutor and by default generate a |
e9acd21
to
00c5715
Compare
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 2a92a67. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
7f6178f
to
d7fc1e3
Compare
d7fc1e3
to
2a92a67
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
The executor generator generates
Expected Behavior
The above code does not make it obvious that an executor has a second
context
argument or that it can return anAsyncIterableIterator
. By typing the function against theExecutor
type the user will have typesafety to know that they are implementing the interface of their executor correctly and an easy way to view the type definition of an executor