Chris Wawer

Based on HAT (Hobbit Application Template), I have writing small apps which use different gems, and i have found little problem(s). Problem with render and view extension: For example in...

string path as first argument in filter isn't enough

1

We can create the same path in different HTTP request type. For example: GET /posts/:id PUT /posts/:id when we add before('/posts/:id') { ... } before filter will be work for...

Problem with fetching archive data

2

I want to use eth_call with a custom block number, which should return archive data. Unfortunately, I have found that in line https://github.com/q9f/eth.rb/blob/main/lib/eth/client.rb#L472 "latest" value is added. Is it possible...

I know that this solution isn't ideal, and there is probably an easier approach. But it works, at least for me. Any support for custom block numbers would be great.

The solution for issue which is described here: https://github.com/q9f/eth.rb/issues/236

Support CAS v3 protocol

1

CAS v3 provides user attributes in a bit different way.

support state params

3

In this changes user can specific state value, it based on omniauth-google-oauth2 strategy. It is very useful when we have multidomain application with one linkedin application.

Origin gem displays the warning: ``` /Users/wafcio/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/origin-2.3.0/lib/origin/aggregable.rb:26: warning: instance variable @aggregating not initialized ``` It can be hard to fix because origin gem is legacy right now.