#dry_rb — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dry_rb, aggregated by home.social.
-
Hanami 2.2.0.beta2 is out!
This beta is a special one: it includes something I’d originally ruled out for 2.2: multiple gateway support!
Now you’re just a single env var away from building a persistence layer that can seamlessly mix and match data from multiple different databases!
Oh, and we added MySQL support. And support for full contract-based params validation.
Next steps: an rc1 and then 2.2 final, all before @rubyconf!
-
Hanami 2.2.0.beta2 is out!
This beta is a special one: it includes something I’d originally ruled out for 2.2: multiple gateway support!
Now you’re just a single env var away from building a persistence layer that can seamlessly mix and match data from multiple different databases!
Oh, and we added MySQL support. And support for full contract-based params validation.
Next steps: an rc1 and then 2.2 final, all before @rubyconf!
-
Hanami 2.2.0.beta2 is out!
This beta is a special one: it includes something I’d originally ruled out for 2.2: multiple gateway support!
Now you’re just a single env var away from building a persistence layer that can seamlessly mix and match data from multiple different databases!
Oh, and we added MySQL support. And support for full contract-based params validation.
Next steps: an rc1 and then 2.2 final, all before @rubyconf!
-
Hanami 2.2.0.beta2 is out!
This beta is a special one: it includes something I’d originally ruled out for 2.2: multiple gateway support!
Now you’re just a single env var away from building a persistence layer that can seamlessly mix and match data from multiple different databases!
Oh, and we added MySQL support. And support for full contract-based params validation.
Next steps: an rc1 and then 2.2 final, all before @rubyconf!
-
Hanami 2.2.0.beta2 is out!
This beta is a special one: it includes something I’d originally ruled out for 2.2: multiple gateway support!
Now you’re just a single env var away from building a persistence layer that can seamlessly mix and match data from multiple different databases!
Oh, and we added MySQL support. And support for full contract-based params validation.
Next steps: an rc1 and then 2.2 final, all before @rubyconf!
-
🌸 Announcing Hanami 2.2.0.beta2
For our second (and final!) beta of 2.2, we’re adding MySQL support, and introducing a powerful way to work across multiple databases.
(pssst, if you’re also a user of param validations inside actions, we have a little treat for you in this release too)
-
🌸 Announcing Hanami 2.2.0.beta2
For our second (and final!) beta of 2.2, we’re adding MySQL support, and introducing a powerful way to work across multiple databases.
(pssst, if you’re also a user of param validations inside actions, we have a little treat for you in this release too)
-
🌸 Announcing Hanami 2.2.0.beta2
For our second (and final!) beta of 2.2, we’re adding MySQL support, and introducing a powerful way to work across multiple databases.
(pssst, if you’re also a user of param validations inside actions, we have a little treat for you in this release too)
-
🌸 Announcing Hanami 2.2.0.beta2
For our second (and final!) beta of 2.2, we’re adding MySQL support, and introducing a powerful way to work across multiple databases.
(pssst, if you’re also a user of param validations inside actions, we have a little treat for you in this release too)
-
Read about ProtoInteractor, a simple business object I created to use with Hanami. It combines:
* The parameter parsing functionality of Hanami Actions.
* Do notation from Dry-Monads.
* Result objects, also from Dry-Monads.Feedback and corrections (especially) are welcome! Please let me know what you think!
https://rossney.net/articles/protointeractor-a-simple-business-object-for-hanami/
-
Read about ProtoInteractor, a simple business object I created to use with Hanami. It combines:
* The parameter parsing functionality of Hanami Actions.
* Do notation from Dry-Monads.
* Result objects, also from Dry-Monads.Feedback and corrections (especially) are welcome! Please let me know what you think!
https://rossney.net/articles/protointeractor-a-simple-business-object-for-hanami/
-
Read about ProtoInteractor, a simple business object I created to use with Hanami. It combines:
* The parameter parsing functionality of Hanami Actions.
* Do notation from Dry-Monads.
* Result objects, also from Dry-Monads.Feedback and corrections (especially) are welcome! Please let me know what you think!
https://rossney.net/articles/protointeractor-a-simple-business-object-for-hanami/
-
Read about ProtoInteractor, a simple business object I created to use with Hanami. It combines:
* The parameter parsing functionality of Hanami Actions.
* Do notation from Dry-Monads.
* Result objects, also from Dry-Monads.Feedback and corrections (especially) are welcome! Please let me know what you think!
https://rossney.net/articles/protointeractor-a-simple-business-object-for-hanami/
-
@swilgosz #hanami #dry_rb #hanamimastery
I would definitely be interested an an episode on this. 👍
-
My November'23 OS Update: Exploring database transaction management in dry-operation and incorporating global error handling to enhance flow classes. Check it out!
https://waiting-for-dev.github.io/blog/2023/12/01/open_source_status_november_2023
-
My November'23 OS Update: Exploring database transaction management in dry-operation and incorporating global error handling to enhance flow classes. Check it out!
https://waiting-for-dev.github.io/blog/2023/12/01/open_source_status_november_2023
-
My November'23 OS Update: Exploring database transaction management in dry-operation and incorporating global error handling to enhance flow classes. Check it out!
https://waiting-for-dev.github.io/blog/2023/12/01/open_source_status_november_2023
-
My November'23 OS Update: Exploring database transaction management in dry-operation and incorporating global error handling to enhance flow classes. Check it out!
https://waiting-for-dev.github.io/blog/2023/12/01/open_source_status_november_2023
-
Here’s my open source status update for September, in which I make a range of small fixes, bend better_errors to our will via a clever li’l patch, kickstart a new dry-rb gem with @waiting_for_dev, and then release Hanami 2.1.0.beta2!
Things are moving, plenty going on. Catch yourself up: https://timriley.info/writing/2023/10/20/open-source-status-update-september-2023/
-
Here’s my open source status update for September, in which I make a range of small fixes, bend better_errors to our will via a clever li’l patch, kickstart a new dry-rb gem with @waiting_for_dev, and then release Hanami 2.1.0.beta2!
Things are moving, plenty going on. Catch yourself up: https://timriley.info/writing/2023/10/20/open-source-status-update-september-2023/
-
Here’s my open source status update for September, in which I make a range of small fixes, bend better_errors to our will via a clever li’l patch, kickstart a new dry-rb gem with @waiting_for_dev, and then release Hanami 2.1.0.beta2!
Things are moving, plenty going on. Catch yourself up: https://timriley.info/writing/2023/10/20/open-source-status-update-september-2023/
-
Here’s my open source status update for September, in which I make a range of small fixes, bend better_errors to our will via a clever li’l patch, kickstart a new dry-rb gem with @waiting_for_dev, and then release Hanami 2.1.0.beta2!
Things are moving, plenty going on. Catch yourself up: https://timriley.info/writing/2023/10/20/open-source-status-update-september-2023/
-
Here’s my open source status update for September, in which I make a range of small fixes, bend better_errors to our will via a clever li’l patch, kickstart a new dry-rb gem with @waiting_for_dev, and then release Hanami 2.1.0.beta2!
Things are moving, plenty going on. Catch yourself up: https://timriley.info/writing/2023/10/20/open-source-status-update-september-2023/
-
TIL Types::Hash.map is still not fully supported by dry-schema/dry-validations. :(
https://github.com/dry-rb/dry-types/commit/04c66608f9d2e4b9e6aacb14e492ea9c13caea4a
#dry_rb #dry_types -
TIL Types::Hash.map is still not fully supported by dry-schema/dry-validations. :(
https://github.com/dry-rb/dry-types/commit/04c66608f9d2e4b9e6aacb14e492ea9c13caea4a
#dry_rb #dry_types -
TIL Types::Hash.map is still not fully supported by dry-schema/dry-validations. :(
https://github.com/dry-rb/dry-types/commit/04c66608f9d2e4b9e6aacb14e492ea9c13caea4a
#dry_rb #dry_types -
TIL Types::Hash.map is still not fully supported by dry-schema/dry-validations. :(
https://github.com/dry-rb/dry-types/commit/04c66608f9d2e4b9e6aacb14e492ea9c13caea4a
#dry_rb #dry_types -
TIL Types::Hash.map is still not fully supported by dry-schema/dry-validations. :(
https://github.com/dry-rb/dry-types/commit/04c66608f9d2e4b9e6aacb14e492ea9c13caea4a
#dry_rb #dry_types -
Solved: use `Types::Symbol.enum(symbol: 'string', ...)` if you want to convert Strings into Symbols.
#dry_rb #dry_types -
Solved: use `Types::Symbol.enum(symbol: 'string', ...)` if you want to convert Strings into Symbols.
#dry_rb #dry_types -
Solved: use `Types::Symbol.enum(symbol: 'string', ...)` if you want to convert Strings into Symbols.
#dry_rb #dry_types -
Solved: use `Types::Symbol.enum(symbol: 'string', ...)` if you want to convert Strings into Symbols.
#dry_rb #dry_types -
Solved: use `Types::Symbol.enum(symbol: 'string', ...)` if you want to convert Strings into Symbols.
#dry_rb #dry_types -
How would you use dry-types/dry-schema to map a finite set of possible Strings to
a finite set of Symbols? `Types::String.enum('string' => :symbol)` only seems to map Strings and Symbols to Strings. I need the output to be Symbols.Input: ['syn', 'ack']
Output: [:syn, :ack] -
How would you use dry-types/dry-schema to map a finite set of possible Strings to
a finite set of Symbols? `Types::String.enum('string' => :symbol)` only seems to map Strings and Symbols to Strings. I need the output to be Symbols.Input: ['syn', 'ack']
Output: [:syn, :ack] -
How would you use dry-types/dry-schema to map a finite set of possible Strings to
a finite set of Symbols? `Types::String.enum('string' => :symbol)` only seems to map Strings and Symbols to Strings. I need the output to be Symbols.Input: ['syn', 'ack']
Output: [:syn, :ack] -
How would you use dry-types/dry-schema to map a finite set of possible Strings to
a finite set of Symbols? `Types::String.enum('string' => :symbol)` only seems to map Strings and Symbols to Strings. I need the output to be Symbols.Input: ['syn', 'ack']
Output: [:syn, :ack] -
How would you use dry-types/dry-schema to map a finite set of possible Strings to
a finite set of Symbols? `Types::String.enum('string' => :symbol)` only seems to map Strings and Symbols to Strings. I need the output to be Symbols.Input: ['syn', 'ack']
Output: [:syn, :ack] -
Clever. dry-validations allows for rules to execute on each value in an Array using `rule(:name).each do ...`.
https://dry-rb.org/gems/dry-validation/1.5/rules/#defining-a-rule-for-each-element-of-an-array
#dry_rb #dry_validations -
Clever. dry-validations allows for rules to execute on each value in an Array using `rule(:name).each do ...`.
https://dry-rb.org/gems/dry-validation/1.5/rules/#defining-a-rule-for-each-element-of-an-array
#dry_rb #dry_validations -
Clever. dry-validations allows for rules to execute on each value in an Array using `rule(:name).each do ...`.
https://dry-rb.org/gems/dry-validation/1.5/rules/#defining-a-rule-for-each-element-of-an-array
#dry_rb #dry_validations -
Clever. dry-validations allows for rules to execute on each value in an Array using `rule(:name).each do ...`.
https://dry-rb.org/gems/dry-validation/1.5/rules/#defining-a-rule-for-each-element-of-an-array
#dry_rb #dry_validations -
Clever. dry-validations allows for rules to execute on each value in an Array using `rule(:name).each do ...`.
https://dry-rb.org/gems/dry-validation/1.5/rules/#defining-a-rule-for-each-element-of-an-array
#dry_rb #dry_validations -
Now that I'm writing HTML forms to pass params to dry-validations/dry-schema, I'm wondering if anyone has built a form builder library that can interpret dry-types and generate the appropriate form fields? Or is that what trailblazer is for?
#dry_rb -
Now that I'm writing HTML forms to pass params to dry-validations/dry-schema, I'm wondering if anyone has built a form builder library that can interpret dry-types and generate the appropriate form fields? Or is that what trailblazer is for?
#dry_rb -
Now that I'm writing HTML forms to pass params to dry-validations/dry-schema, I'm wondering if anyone has built a form builder library that can interpret dry-types and generate the appropriate form fields? Or is that what trailblazer is for?
#dry_rb -
Now that I'm writing HTML forms to pass params to dry-validations/dry-schema, I'm wondering if anyone has built a form builder library that can interpret dry-types and generate the appropriate form fields? Or is that what trailblazer is for?
#dry_rb -
Now that I'm writing HTML forms to pass params to dry-validations/dry-schema, I'm wondering if anyone has built a form builder library that can interpret dry-types and generate the appropriate form fields? Or is that what trailblazer is for?
#dry_rb -
dry-schema newb question: how do I correctly coerce non-empty String -> Integer, empty String -> nil?
Trying `optional(:foo).value(:integer)` and
`optional(:foo).maybe(:integer)` both raise dry-validation errors when given either an empty-String or a numerical String. I suspect I'm making a really basic mistake here.
#dry_rb -
dry-schema newb question: how do I correctly coerce non-empty String -> Integer, empty String -> nil?
Trying `optional(:foo).value(:integer)` and
`optional(:foo).maybe(:integer)` both raise dry-validation errors when given either an empty-String or a numerical String. I suspect I'm making a really basic mistake here.
#dry_rb -
dry-schema newb question: how do I correctly coerce non-empty String -> Integer, empty String -> nil?
Trying `optional(:foo).value(:integer)` and
`optional(:foo).maybe(:integer)` both raise dry-validation errors when given either an empty-String or a numerical String. I suspect I'm making a really basic mistake here.
#dry_rb -
dry-schema newb question: how do I correctly coerce non-empty String -> Integer, empty String -> nil?
Trying `optional(:foo).value(:integer)` and
`optional(:foo).maybe(:integer)` both raise dry-validation errors when given either an empty-String or a numerical String. I suspect I'm making a really basic mistake here.
#dry_rb -
dry-schema newb question: how do I correctly coerce non-empty String -> Integer, empty String -> nil?
Trying `optional(:foo).value(:integer)` and
`optional(:foo).maybe(:integer)` both raise dry-validation errors when given either an empty-String or a numerical String. I suspect I'm making a really basic mistake here.
#dry_rb -
How do you specify a String or Regexp type in a dry-schema?
#dry_rb -
How do you specify a String or Regexp type in a dry-schema?
#dry_rb