Kirill Zaitsev

At my job, we are working fine with the `async` because we already have the sidekiq in our stack. I can't understand why `async` can't be an optional way to...

@solnic unfortunately no ```rb require 'dry/schema' MySchema = Dry::Schema.Params do required(:list).array do schema do required(:some_item).filled(:str?) end end end puts MySchema.key_map.write(unexpected_key: 1, list: [{some_items: 'str', unexpected_key: 2}]) # => {:list=>[{}]} ```...

O sorry my bad, i have a typo

Perhaps you should require an explicit type declaration before "each" expression? This allows avoiding some disasters when schema can pass unexpected params which not a part of the schema.

hello, @migmartri as i know, it's not possible out of box, but you can write custom data-wrapper and model parser for this.

For example: ```rb # Wrapper class DataWrapper attr_reader :model attr_reader :key attr_reader :is_array attr_reader :wrapper_name def initialize(model, wrapper_name: nil, key: :data, is_array: false) @model = model @wrapper_name = wrapper_name @key...

@eropple Hello, can you provide some examples of code or spec for this feature?

Looks like, ancestors doesn't contains: `Representable::Decorator` ```rb Presenters::ApplicationPresenter.ancestors => [Presenters::ApplicationPresenter, Grape::Roar::Representer, Roar::JSON::HAL::LinksReader, Roar::JSON::HAL::Resources, Roar::JSON::HAL::Links::InstanceMethods, Roar::Hypermedia, Roar::JSON::HAL::Links, Roar::JSON::InstanceMethods, Representable::JSON, Representable, Representable::Hash, Roar::Representer, Roar::JSON, Roar::JSON::HAL] ``` `grape-swagger-representable`, doesn't support's `roar`, but `roar`...

Any updates?

Hello, @Fs00. I can understand your point, this might be reasonable for some projects to set the default field type by the naming convention (if the type is not specified)....