Roman Heinrich
Roman Heinrich
here is an example how the error message would look like: ``` ParamContractError: Contract violation for argument 1 of 1: Expected: (KeywordArgs[{:guid=>String, :occurred_at=>DateTime, :created_by_id=>Contracts::Builtin::Num}]) Actual: {:guid=>"4fea1b56-3218-4c4c-a2ce-6db42d8e445f", :occurred_at=>"1", :test1=>1} Missing Contract:...
Hey @egonSchiele, good to hear from you! Because the discussion here ended kinda abruptly and I liked the idea of contracts for Ruby, I have continued my work on a...
@egonSchiele thx for staying cool! If you don't work in Ruby anymore, maybe you could look around for another maintainer / co-maintainer with rights to merge / push to Rubygems?...
here is another project where the original maintainer looked for new maintainers: https://github.com/fgrehm/vagrant-cachier/issues/143#issuecomment-273523976
also possible alternative: https://github.com/jonasschmidt/ex_json_schema simpler API, less functionality (in a good way), less dependencies.
sounds great, all for offloading responsibility. 👍 we can always pick this up when this becomes a pain point
a bit offtopic: we should have labels with prios / or difficulty levels :)
Any news on this issue? It seems like there could be some solutions, if given enough priority.
Really looking forward to it!
Hello Brian, we have some analytical requirements and having aggregations support is absolute must here.