Skip to content

Conversation

@LadyBluenotes
Copy link
Member

No description provided.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@netlify
Copy link

netlify bot commented Nov 27, 2025

Deploy Preview for solid-docs failed. Why did it fail? →

Name Link
🔨 Latest commit 001840b
🔍 Latest deploy log https://app.netlify.com/projects/solid-docs/deploys/693afa72023a4f0007889296

@brenelz
Copy link
Collaborator

brenelz commented Dec 1, 2025

Deploy preview failed for some reason

@brenelz
Copy link
Collaborator

brenelz commented Dec 1, 2025

Looks like someone already updated createComputed here

#1358

@LadyBluenotes LadyBluenotes enabled auto-merge (squash) December 1, 2025 20:40
Copy link
Collaborator

@amirhhashemi amirhhashemi left a comment

Choose a reason for hiding this comment

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

One overall issue is that these reference pages don't strictly follow Diataxis. They include quite a bit of explanatory material and an explanatory tone. I've been spending a lot of time trying to ensure that at least the reference pages follow Diataxis more strictly. Honestly, I'm not sure it's worth the effort at this point. If improving Diataxis compliance isn't a goal of this PR, I'm perfectly fine with that.

Copy link
Collaborator

@amirhhashemi amirhhashemi left a comment

Choose a reason for hiding this comment

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

I highly recommend running Prettier on these. There are a lot of formatting issues.

Comment on lines 95 to 96
Reactive data source whose non-nullish and non-false values are passed to the fetcher.
When the source changes, the fetcher is automatically re-run.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Reactive data source whose non-nullish and non-false values are passed to the fetcher.
When the source changes, the fetcher is automatically re-run.
Reactive data source whose value, when not `undefined`, `null`, or `false`, is passed as the first argument to the fetcher.
When the source changes, the fetcher automatically re-runs.

I think "nullish" can be a bit confusing.

Copy link
Contributor

@atk atk Dec 10, 2025

Choose a reason for hiding this comment

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

But this is incorrect. 0 and "" are also false. Maybe try:

"Reactive data source whose value, when turned into a boolean is not false, will be passed as the first argument to the fetcher. If it is false, the fetcher will not be called. Values that become false include undefined, null, the number zero, and empty strings."

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated - let me know what you think of the rephrase.

Copy link
Collaborator

Choose a reason for hiding this comment

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

As far as I can tell from the code and my tests, only null, undefined, and false are not passed. Other falsy values like 0 and "" are still passed.

Playground: https://playground.solidjs.com/anonymous/925f6243-cf68-496e-936b-3f3221b17cca

Co-authored-by: Amir Hossein Hashemi <[email protected]>
@LadyBluenotes LadyBluenotes changed the title createSignal updates createSignal , createResource updates Dec 11, 2025
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.

5 participants