Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add default behavior for user/global layer lookup #2247

Closed
zFernand0 opened this issue Aug 27, 2024 · 3 comments
Closed

Add default behavior for user/global layer lookup #2247

zFernand0 opened this issue Aug 27, 2024 · 3 comments
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have Stale

Comments

@zFernand0
Copy link
Member

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

Originally posted by @traeok in #2241 (comment)

@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad Aug 27, 2024
@JTonda JTonda added enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have labels Sep 9, 2024
Copy link

github-actions bot commented Sep 9, 2024

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.

@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe CLI Squad Sep 9, 2024
Copy link

github-actions bot commented Dec 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the Stale label Dec 8, 2024
Copy link

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 23, 2024
@github-project-automation github-project-automation bot moved this from Low Priority to Closed in Zowe CLI Squad Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have Stale
Projects
Status: Closed
Development

No branches or pull requests

2 participants