Ability to access unfiltered request parameters

[hanami]

Ability to access unfiltered request parameters

[AlfonsoUceda]

Ok, you don't have to params[:return_to] because params only has first_name, last_nameand email, isn't it?

Yes, then we have an API separating the whitelisted params and all params or no-whitelisted params.

API

• params.raw[:whatever]
• params.whitelisted[:other]

What do you think? I prefer whitelisted than original

[weppos]

I don't think we should have two API. params should always represent the expected, (filtered if required) param list.

However, there should be a way to access the original, unfiltered list. If no param filtering is set, then params and params.original (or whatever name is) would be the same.

[AlfonsoUceda]

Ok, I prefer too, this change doesn't break params api and it only adds the original or raw params. 👍

[jodosha]

API

Quoting @weppos

I don't think we should have two API. params should always represent the expected, (filtered if required) param list.

👍 This will keep the existing whitelisting semantic.

I'm for naming it #raw.

Technical implementation

We can rename Params#_params with Params#_raw.

This method should memoize the result of that computation in @raw. This should be a Lotus::Utils::Attributes instance, in order to guarantee "indifferent access" until we drop support for 2.2-.

As last thing, we should expose an attr_reader :raw.