re rspec, I so agree with you, I would say more - RSpec's crazy mocking capabilities has done more harm than good. I really wish RSpec's core team decided to trim that API to the very minimum.
(oh and I should mention I am a huge RSpec fan)
@solnic Would be interesting to see how he approaches that problem... Right now this kinda blocks me from adopting Hanami to my next project. Which leaves me kinda lost I guess - I feel like my best shot now is to assemble everything on my own, Roda\Sinatra for routing + ROM (I build an API, all jsons, no need for views at all)
swapping routing front-ends in this architecture really is easy
@solnic yes, I am also a huge RSpec fan but indeed they, as many others, have taken the fact that Ruby is an interpretable, not complied, language, to a bad place. The thing is, it works OK for small CRUD apps but when you have bigger stuff with lots of logic, it's just one big procedural mess :(
Any idea how to make this work?
require "dry/container"
module Core
class Container
extend Dry::Container::Mixin
register("transaction") do |input, &block|
result = nil
begin
ActiveRecord::Base.transaction do
result = block.call(Dry::Monads::Success(input))
raise ActiveRecord::Rollback if result.failure?
result
end
rescue ActiveRecord::Rollback
require "pry"; binding.pry
result
end
end
end
endI'm getting the following error:
Dry::Transaction::InvalidResultError: step +transaction+ must return a Result objectI guess because the ActiveRecord::Rollback is not being rescued.
i have a question on
dry-validation... is it possible to export a JSON schema file based on a dry schema? I find the dry/ruby stuff much easier to read but my work still depends on JSON schemas
In essence, I want it to be strict.
@alexandrubeu nothing working OOTB. You can create a container on every request, though, with a certain amount of effort this should be good enough. At least I did this, but now I'm experimenting on providing context-aware dependencies using a different approach. If it works fine (atm it appears so) I'm going to build another library for this, it's a matter of months
Hey @flash-gordon, not sure if you had the chance to check this dry-rb/dry-types#277 out? I think we're just waiting for your input. No hurry, though, just don't want the momentum to get lost.
I'm working at a company and we've been building an API to replace our legacy java platform.. everything has been going well in the past year up until very recently. Our ruby application (the api) is dockerized and deployed to AWS' Elastic Container Service.
However, after the latest changes, when I try to deploy (building and publishing via docker), on the bundle install step (from my dockerfile), I receive this error: `fatal: Could not parse object '#{some long hash}'.
Any idea how I could fix this? @timriley @solnic
@knazary Also, we cannot provide support related to application deployment. This is outside our purview as gem developers.
got it.
In the meantime, perhaps there’s a checked out copy of that commit in your local bundle cache
However, do NOT let that prevent you from doing the right thing and getting off that repo ASAP
