Skip to content

Lock resources from ResourceItems; add "DoNotLock" state as new default.

T.J. Corona requested to merge tjcorona/smtk:add_pass_permission into master

In order for operations to call operations on a resource passed into the top-level operation, there needs to be a mechanism for skipping resource locking. This commit adds lock state "DoNotLock", which bypasses resource locking. It is now the default state for both ResourceItems and ComponentItems. Also, if the lock state is "DoNotLock" then no value is transcribed to the attribute file.

When the concept of locking/unlocking resources was added to smtk::operation::Operation, ResourceItems didn't exist. When they were added, I forgot to update Operation's locking/unlocking logic to support them. This MR fixes that.

Edited by T.J. Corona

Merge request reports