rohityadavcloud commented on pull request #6081: URL: https://github.com/apache/cloudstack/pull/6081#issuecomment-1064399633
I suppose this is classical debate whether to show/hide an action/element or show them as disabled to the end user. Disabling a widget/component signals explicitly the information that there exists a feature/widget/component that for some reason the user isn't allowed to access (but by doing that we make the user aware that the feature exists). Hiding the feature/component is another approach where we don't want the user to even know about the feature, that it even exists. Projects is generally a fundamental/default feature to CloudStack, I suppose if you have a role that disables that, then you're probably disabling not just the listProjects API but perhaps the entire projects feature. In that case, hiding the drop-down entirely makes sense. Let us know @BryanMLima your thought process around this, what led to this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
