It's incredibly clever for sure but I feel like it's a massive hack for things like the DB obfuscation feature.
If my access is read-only then it's probably fine but if I have write access and I write back a whole row (my DB tool only updates the changes I think but IDK if every tool works that way) isn't it going to write back the "cleaned"/"hidden" data?
Again, it's very impressive and clever but I just worry I'd blow my foot off by accident.
Thanks for the feedback and kind words! You bring up a valid concern. Let me clarify how it works:
The obfuscation is designed to be intelligent and context-aware. When you have write access and make changes, hoopdev ensures that only the intended modifications are written back, not the obfuscated data. We've implemented safeguards to prevent accidental overwrites with "cleaned" or "hidden" data.
Let me know if you have any specific scenarios or tools you'd like to test with.
Comments
It's incredibly clever for sure but I feel like it's a massive hack for things like the DB obfuscation feature.
If my access is read-only then it's probably fine but if I have write access and I write back a whole row (my DB tool only updates the changes I think but IDK if every tool works that way) isn't it going to write back the "cleaned"/"hidden" data?
Again, it's very impressive and clever but I just worry I'd blow my foot off by accident.
Thanks for the feedback and kind words! You bring up a valid concern. Let me clarify how it works:
The obfuscation is designed to be intelligent and context-aware. When you have write access and make changes, hoopdev ensures that only the intended modifications are written back, not the obfuscated data. We've implemented safeguards to prevent accidental overwrites with "cleaned" or "hidden" data.
Let me know if you have any specific scenarios or tools you'd like to test with.