Adding skip_fields option at Yancy::Plugin::Form::Bootstrap4 form_for

[pavelsr]

E.g. I have schema

CREATE TABLE users (
  `id` INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  `username` VARCHAR(255) NOT NULL,
  `email` VARCHAR(255) NOT NULL,
  `phone` VARCHAR(255) NOT NULL,
  `password` VARCHAR(40) NOT NULL,
  `created` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
   `is_admin` BOOL,
  UNIQUE KEY (`username`,`email`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci;

If I call form_for there is no way to skip fields like id, created, is_admin which are typically not required for user input.

[pavelsr]

Merge request: #94

[preaction]

This was solved in a couple ways:

• The properties stash now controls which fields get shown in a form_for form (commit d1a7e8d)
• Read-only fields are not shown by default when using form_for (commit 2b78e7b9)

Thanks for reporting this and providing a patch!

[pavelsr]

Hey Doug! Seems like we should add skip_fields arg in addition to properties I found at least one use case where it could be extremelly usefull - skipping user_id field in item add/edit form in multiTenant apps.

[pavelsr]

Code example:

# controller:
$user_route->get('/bank_details/edit/:id')->to( 'yancy-multi_tenant#get', schema => 'bank_details', template => 'bank_detail_edit' ); 
# bank_detail_edit.html.ep
%= $c->yancy->form->form_for( 'bank_details', skip_fields => [ 'id', 'user_id' ] ); 

For now I have to use long and not elegant construction:

properties => [ grep { $_ !~ /id/ } keys %{ $c->yancy->backend->schema->{bank_details}{properties} } ]