technically the lease work is not part of #5844, however, it will need to updated similarly to embargoes and I do not see a ticket for it. so the work is being done here wile the embargo work is fresh on our minds.

co-authored-by: braydon <braydon.justice@1268456bcltd.ca>

co-authored-by: braydon <braydon.justice@1268456bcltd.ca>

… embargo pattern

…hat we can create and deactivate them too.

…vate leases.

…e in the future before saving an embargo/lease.

ref: #6126
ref: #5844

… being passed to Hyrax::Transactions::Steps::Save#call

…rect details

…r better ux and ui

…unsaved leases

…rsister#save because we have already done validation as a Valkyrie object.

co-authored-by: rob <rob@scientist.com>

af_object.lease.class has the same name as resource.lease.class; however, each class has a different object_id.
so a type mismatch happens. the code below coerces the one object into the other.
TODO: fix this!

co-authored-by: jeremy <jeremy.n.friesen@gmail.com>

…e because valkyrie does not respond to `valid?`

…ide Wings::ActiveFedoraConverter#apply_attributes_to_model

…ect "ActiveRecord::RecordNotFound" isntead of "RuntimeError".

previously running `Hyrax.persister.save(resource: admin_set)` in Hyrax::AdminSetCreateService#create! would have failed. however, with the change in commit 9b64c54 we are no longer validating valkyrie turned active fedora objects.
this means a failure happens in app/models/sipity/workflow.rb:55 since the admin set is invalid.

…ty arrays in Wings::ModelTransformer#append_embargo and Wings::ModelTransformer#append_lease. we are now setting the values to empty arrays in Hyrax::Forms::Embargo/Lease and Hyrax::Forms::WorkLeaseForm/WorkEmbargoForm

… lease has been added to its parent work

… the af_object lease inside #apply_attributes_to_model.this avoids the "Attempting to recreate existing ldp_source" error in dozens of specs

…ource responds to the `lease` method before calling it

…verted item to have the same lease_id as the original resource

…ling so that generic_works_controller_json_spec.rb:58 passes. should be a green pipeline!

co-authored-by: jeremy <jeremy.n.friesen@gmail.com>

…pec.rb

by default we will not validate the converted af_object because validations should have been run on the Valkyrie created object. however, there are situations where we will have created an ActiveFedora object while `Hyrax.config.use_valkyrie?` is TRUE. (see: spec/controllers/hyrax/generic_works_controller_json_spec.rb:59)

this change accounts for that use case.

…x.config.use_valkyrie is true

… ones.

accounting for a work with file set that did not have a lease, then added one.
a work that was created with a file set and lease,
plus a work that already had a lease and added a file set.

…ts previous expectations by passing `perform_af_validation: true` in `Hyrax::AdminSetCreateService#create!`

…s funny business in Wings::ActiveFedoraConverter#apply_attributes_to_model in order for spec/wings/active_fedora_converter_spec.rb:365 to pass! 🎉

now lets hope it also passes in ci. 😩

…ameter combo to #valkyrie_save, and therfore Persister#save

…dora_converter.rb

…ices/hyrax/admin_set_create_service_spec.rb:294

…idiculously tricky and I wish we did not have to.