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
Many IConfig.api.layer methods perform operations based on the specified layer.
It'd be nice to have some default behavior based on Trae's comment below 🙏🏽
Curious to get your thoughts on making user and global optional? We can fallback to false if the property is not provided, but this would allow a developer to call secureFieldsWithDetails without having to specify both user and global:
profileInfo.secureFieldsWithDetails({user: true});// project user config// or...profileInfo.secureFieldsWithDetails({global: true});// global, non-user config
Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.
Many
IConfig.api.layer
methods perform operations based on the specified layer.It'd be nice to have some default behavior based on Trae's comment below 🙏🏽
Curious to get your thoughts on making
user
andglobal
optional? We can fallback tofalse
if the property is not provided, but this would allow a developer to callsecureFieldsWithDetails
without having to specify bothuser
andglobal
:Originally posted by @traeok in #2241 (comment)
The text was updated successfully, but these errors were encountered: