Skip to content
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

[ESLint] Remove require-event-emitter-type rule #10423

Closed
maxpatiiuk opened this issue Sep 27, 2024 · 4 comments
Closed

[ESLint] Remove require-event-emitter-type rule #10423

maxpatiiuk opened this issue Sep 27, 2024 · 4 comments
Assignees
Labels
4 - verified Issues that have been released and confirmed resolved. breaking change Issues and pull requests with code changes that are not backwards compatible. estimate - 2 Small fix or update, may require updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality p - low Issue is non core or affecting less that 10% of people using the library tooling Issues relating to build system fixes or improvements.

Comments

@maxpatiiuk
Copy link
Member

Priority impact

p - low

Summary

Blocked by #10310

Calcite developed an require-event-emitter-type ESLint rule.
Such rule is not necessary in Lumina because the default event emitter type is void rather than any.
Also, if event emitter type is not void, then the first argument in .emit() is mandatory (in Stencil it was always optional, leading to possible bugs if you forgot to provide the payload)

Desired Outcome

Remove the require-event-emitter-type ESLint rule after the migration.

Resources

No response

@maxpatiiuk maxpatiiuk added tooling Issues relating to build system fixes or improvements. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Sep 27, 2024
@github-actions github-actions bot added the p - low Issue is non core or affecting less that 10% of people using the library label Sep 27, 2024
@jcfranco jcfranco added the blocked This issue is blocked by another issue. label Sep 27, 2024
@jcfranco
Copy link
Member

This was addressed by #10482.

@jcfranco jcfranco added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 0 - new New issues that need assignment. labels Nov 26, 2024
Copy link
Contributor

Installed and assigned for verification.

@jcfranco jcfranco added p - high Issue should be addressed in the current milestone, impacts component or core functionality estimate - 2 Small fix or update, may require updates to tests. breaking change Issues and pull requests with code changes that are not backwards compatible. and removed blocked This issue is blocked by another issue. needs triage Planning workflow - pending design/dev review. labels Nov 26, 2024
Copy link
Contributor

Issue #10310 has been closed, this issue is ready for re-evaluation.

cc @geospatialem,@DitwanP

@DitwanP
Copy link
Contributor

DitwanP commented Nov 26, 2024

🍡 Verified

@DitwanP DitwanP closed this as completed Nov 26, 2024
@DitwanP DitwanP added 4 - verified Issues that have been released and confirmed resolved. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified Issues that have been released and confirmed resolved. breaking change Issues and pull requests with code changes that are not backwards compatible. estimate - 2 Small fix or update, may require updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality p - low Issue is non core or affecting less that 10% of people using the library tooling Issues relating to build system fixes or improvements.
Projects
None yet
Development

No branches or pull requests

4 participants