Skip to content
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: fix the description of when to use the synchronous function #3849

Merged
merged 2 commits into from
Nov 16, 2024

Conversation

vvanglro
Copy link
Contributor

@vvanglro vvanglro commented Nov 7, 2024

Description

Closes

@vvanglro vvanglro requested review from a team as code owners November 7, 2024 09:48
@github-actions github-actions bot added area/docs This PR involves changes to the documentation size: small type/docs pr/external Triage Required 🏥 This requires triage labels Nov 7, 2024
Copy link
Member

@sobolevn sobolevn left a comment

Choose a reason for hiding this comment

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

I think that this change makes the whole phrase easier. Thank you!

@cofin cofin enabled auto-merge (squash) November 16, 2024 00:31
@cofin cofin merged commit 98933a3 into litestar-org:main Nov 16, 2024
24 checks passed
Copy link

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3849

@@ -101,7 +101,7 @@ When to use a synchronous function
----------------------------------

As an inverse of the previous paragraph, it follows that synchronous functions should
be used for non-blocking, non-computationally intensive tasks. The synchronous execution
be used for non-io intensive tasks. The synchronous execution
Copy link
Member

Choose a reason for hiding this comment

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

This makes it sound like you should use synchronous functions for lightweight IO tasks, which is the opposite of what the paragraph is trying to say

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs This PR involves changes to the documentation pr/external pr/internal size: small Triage Required 🏥 This requires triage type/docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants