-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Update docs to recommend upfront module definition (i.e. Types = Dry.Types()
)
#432
base: main
Are you sure you want to change the base?
Conversation
@solnic @flash-gordon — are you happy with this? If so, I'll merge this and actually make sure we have a 1.5 version of the docs published at dry-rb.org. |
Despite it being (somewhat unconventionally) downcased, this is proper noun and not a piece of code, so we shouldn't show it as such.
@@ -15,7 +15,7 @@ Built-in types are grouped under 6 categories: | |||
|
|||
### Categories | |||
|
|||
Assuming you included `Dry::Types` ([see instructions](docs::getting-started)) in a module called `Types`: | |||
Assuming you've defined your own `Types` module ([see instructions](docs::getting-started)): |
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.
How do you feel about changing the assertion to one that would be more indicative that they should do this, rather than conditional that they might have.
Assuming you've defined your own `Types` module ([see instructions](docs::getting-started)): | |
After you've defined your own `Types` module ([see instructions](docs::getting-started)): |
As agreed, this is our recommendation to resolve the issue raised in #422.
Most of our code examples depend on a
::Types
module having been already created, so to make sure those examples are as clear as possible, I've also addedTypes = Dry.Types()
in front of any grouping of code examples.Made a few other very minor adjustments along the way, too.
Resolves #422