You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of SOPS is functionally based. This is good for programs that rely on transforming data. However, it's beginning to get unwieldy with all of the state passing it is doing (e.g. digest, iv, key, and in #47unencrypted_suffix).
I suggest considering a refactor to swap out the core with something more class based so state is always located on self. I will create a gist to provide examples of what I mean.
The text was updated successfully, but these errors were encountered:
This is actually a duplicate of #3, but no one had time to work on it. That said, I agree wholeheartedly, but I'll close as duplicate and move your comment to #3.
The current implementation of SOPS is functionally based. This is good for programs that rely on transforming data. However, it's beginning to get unwieldy with all of the state passing it is doing (e.g.
digest
,iv
,key
, and in #47unencrypted_suffix
).I suggest considering a refactor to swap out the core with something more class based so state is always located on
self
. I will create a gist to provide examples of what I mean.The text was updated successfully, but these errors were encountered: