GNOME Bugzilla – Bug 653233
Ensure that FieldDetails are immutable to backends
Last modified: 2018-08-04 08:28:36 UTC
As discussed with Alex on IRC, we should ensure (and document) that backends can't modify FieldDetails instances. Instead, they should replace instances of FieldDetails they want to change with new instances, which have been deep copied and modified as appropriate. This means that clients can safely modify FieldDetails instances that they're handed, and re-use them when updating properties without having to worry about breaking the internal state of a backend.
(In reply to comment #0) > This means that clients can safely modify FieldDetails instances that they're > handed, and re-use them when updating properties without having to worry about > breaking the internal state of a backend. Bzzt. This means that clients can safely *re-use FieldDetails instances as read-only* when updating properties.
Punting bugs that won't be fixed by Folks 0.6.0.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/folks/issues/25.