Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

test: add valid example for empty defineEmits #2914

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

Closed

Conversation

Copy link

@Sysix Sysix commented Aug 3, 2025

Covering this part of the code:

if (emptyDefineEmits) {
if (!hasDefaultExport) {
// Custom events are not defined.
context.report({
node: emptyDefineEmits,
messageId: 'notDefined'
})
}

Found in oxc-project/oxc#12545

Copy link

changeset-bot bot commented Aug 3, 2025

⚠️ No Changeset found

Latest commit: ce26e0d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Member

I don't understand, could you please explain in more detail?

Copy link
Author

Sysix commented Aug 3, 2025

I don't understand, could you please explain in more detail?

It just extends the test suite with this special use case. (See linked code part).
Do be fair, I do not know if this is valid in the real world. But the rule allows it.

I am currently working on the implementation of the rule in oxlint.
This test should help to be consistent across different tools.
oxlint will generate their test code from test source code of the plugin.

If you think, this is not helpful as a test case, feel free to close.
I wanted to be sure we do not include inconsistency between both tools.

Copy link
Member

If you think, this is not helpful as a test case, feel free to close.

I'll close it.

graphite-app bot pushed a commit to oxc-project/oxc that referenced this pull request Aug 27, 2025
related #11440
https://github.com/vuejs/eslint-plugin-vue/blob/master/docs/rules/valid-define-emits.md
Extended the docs and tests to cover (non) empty `defineEmits()` with `export default` of other script block.
Related vuejs/eslint-plugin-vue#2914 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /