-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: fleshed out dedicated Architecture section #4124
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
docs: fleshed out dedicated Architecture section #4124
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✔️ Deploy Preview for typescript-eslint ready! 🔨 Explore the source changes: 26d20b0 🔍 Inspect the deploy log: https://app.netlify.com/sites/typescript-eslint/deploys/61906420e40c610007885e2b 😎 Browse the preview: https://deploy-preview-4124--typescript-eslint.netlify.app |
Nx Cloud ReportCI ran the following commands for commit 26d20b0. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch Sent with 💌 from NxCloud. |
Co-authored-by: Armano <armano2@users.noreply.github.com>
docs/development/CUSTOM_RULES.md
Outdated
create(context) { | ||
return { | ||
TSInterfaceDeclaration(node) { | ||
if (/\p{Lu}/.test(node.id.name[0])) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait - what is this regex style? Shouldn't it be /[a-z]/
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://unicode.org/reports/tr18/#General_Category_Property
...except, I'm finding it to not be working in my dev tools, so I'll just go ahead and switch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL - i'd never seen it before!
I never mess with unicode though heh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another way to do this which would let it work independent of latin characters is
if (node.id.name[0].toUpperCase() === node.id.name[0]) {
But it's a bit more obtuse for people to understand in a tutorial...!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work dude! it all is looking good to me!
come on dictionary - it was added to oxford in 2018 - https://english.stackexchange.com/a/246562 |
PR Checklist
Overview
Creates a
Development
section with sub-sections forArchitecture
andCustom Rules
.A few organizational touchups:
Guides
shorthand section (since everything there is a guide at the moment)Development > Architecture
Was there anything else we should cover for third-party folks writing their own plugins?