Sorry about that, didn't mean to mislead anyone.
I think I clearly state in the library that it is only for visual purposes it is NOT secure in anyway by design.
Of course not. I just suggest you change the name to "activate" or "hide" rather than "safe". Because "safe" gives the impression of being a security feature.
From my experience so far, the code behind the feature flags is shipped, but is not available to the user in the production. Talking from the the frontend perspective though, not sure if in native development we can remove code behind the disabled feature flags in compile step.
No. Feature flags are normally used to ignore specific parts of your code in the deployment so they wont get shipped.
SafeView "hides" existing components.
visually
they still exist when you look in your developer tools.
Thanks Lars, SafeView purpose is not to secure your sensitive information.
You can look at it more like a showcase/presentaion helper.
Hmm then it's not really secure or "safe".
It's just activating and deactivating.
What did you think the point of it was?
I don't know.. but "safe" doesn't seem like the right word to use here.
When I read the title of the post, "sensitive information" makes me think of API secrets..
If I want to hide something visually, I can provide a global CSS ID for the same purpose myself...
My thought exactly , I'd rather have a component which perhaps encrypts the data or redacts it on toggle or component render.
yeah.. i was thinking something similar.
Sorry about that, didn't mean to mislead anyone.
I think I clearly state in the library that it is only for visual purposes it is NOT secure in anyway by design.
Of course not. I just suggest you change the name to "activate" or "hide" rather than "safe". Because "safe" gives the impression of being a security feature.
But good work and kudos for your efforts.
You sure about that @larsonnn ?
From my experience so far, the code behind the feature flags is shipped, but is not available to the user in the production. Talking from the the frontend perspective though, not sure if in native development we can remove code behind the disabled feature flags in compile step.
We're using feature flags like in a simple if else statement. So the code is shipped and we can switch the flag on and off at runtime.
I'm sure a compile step could remove the code behind the flag, but then you couldn't toggle the flags at runtime
Thanks for sharing your experience :)