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

Add blog to website #132

Closed
wants to merge 4 commits into from
Closed

Add blog to website #132

wants to merge 4 commits into from

Conversation

IMax153
Copy link
Member

@IMax153 IMax153 commented Jun 29, 2023

No description provided.

@netlify
Copy link

netlify bot commented Jun 29, 2023

Deploy Preview for effect-website failed.

Name Link
🔨 Latest commit 07bb5ab
🔍 Latest deploy log https://app.netlify.com/sites/effect-website/deploys/64eaf704880f4200089d02b5

The first step to achieve type safety in error management as one may imagine is to define errors, let's have a look at a usual piece of code with the objective of improving its safety.

```ts
import * as S from "@effect/schema/Schema"
Copy link
Member Author

Choose a reason for hiding this comment

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

Suggestion:

Given that we explicitly recommend fully qualified name-spaced imports in the documentation, I would suggest being explicit in the blog as well. I.E:

import * as Schema from "@effect/schema/Schema"

@mikearnaldi mikearnaldi deleted the chore/blog branch July 13, 2024 08:06
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.

3 participants