Skip to content

Improves readability of code examples - #224

Open
tomasbonco wants to merge 3 commits into
tc39:mainfrom
tomasbonco:patch-1
Open

tomasbonco wants to merge 3 commits into
tc39:mainfrom
tomasbonco:patch-1

Conversation

@tomasbonco

Copy link
Copy Markdown

Signals themselves are quite complex. Aim of this small PR is to slightly improve readability of code samples. I hope especially beginners and devs not familiar with the topic appreciate it.

  • When comparing, using === instead of == is just a good practice. Additionally, stops reader from questions "Why they didn't use ===? Can this be null or undefined? Do I need to read docs?".
  • Changing let to const separates things that change from those that don't change, so reader don't have to keep in mind all variables.
  • Adding extra brackets to for emphasis there is a code on the same line and reader should not jump directly to the next line.

Improves readability especially for beginners.
* When comparing, using `===` instead of `==` is just a good practice. Additionally, stops reader from questions "Can this be null or undefined? Do I need to read docs?".
* Changing `let` to `const` separates things that change from those that don't change, so reader don't have to keep in mind all variables.
* Adding extra brackets to `for` emphasis there is a code on the same line and reader should not jump directly to the next line.
Comment thread README.md Outdated
Comment thread README.md
export function effect(cb) {
let destructor;
let c = new Signal.Computed(() => { destructor?.(); destructor = cb(); });
const c = new Signal.Computed(() => { destructor?.(); destructor = cb(); });

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same should we go multiline here ?

@tomasbonco tomasbonco May 19, 2024 •

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I know this is sort of personal taste, but in my opinion this is acceptable. Lambda functions are often one-liners and the content in this case is not too complex. I assume a reader is used to reading the rest of the line. Understanding the purpose of the code is going to be the issue, but not its style.

@tomasbonco
tomasbonco requested a review from JeanMeche May 19, 2024 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants