Skip to content

feat(plugins/naming-convention): add 'context-name' rule to enforce n… #952

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

Merged
merged 5 commits into from
Feb 28, 2025

Conversation

Rel1cx
Copy link
Owner

@Rel1cx Rel1cx commented Feb 28, 2025

…aming conventions for contexts

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Docs
  • New Binding issue #___
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes, and the changes were approved in issue #___
  • No

Checklist

  • When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
  • I have added a convincing reason for adding this feature, if necessary

Other information

Sorry, something went wrong.

Copy link

vercel bot commented Feb 28, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
eslint-react ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 28, 2025 11:53pm

…aming conventions for contexts
@Rel1cx Rel1cx merged commit b73d26b into main Feb 28, 2025
8 of 9 checks passed
@Rel1cx Rel1cx deleted the context-name branch March 2, 2025 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
React 19 Type: New Rule Introduce a new rule
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant