-
Notifications
You must be signed in to change notification settings - Fork 378
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
refactor: clean up the 'slot' abstraction for abs-h #3193
Conversation
@@ -4,7 +4,7 @@ | |||
export const OBFUSCATED_VALUE = '*****'; | |||
|
|||
export interface ISettingManager { | |||
get(slot?: string, obfuscate?: boolean): Promise<any | null>; | |||
set(slot: string, settings: any): Promise<void>; | |||
get(obfuscate?: boolean): Promise<any | null>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also take the chance of remove this obfuscate
feature, @cwhitten what do you think? I think we chatted about this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's leave it in for now ad revisit once some customers have successfully deployed Composer and we get some additional feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, leave one question for chris
* clean setting slot related code * remove abshost flag Co-authored-by: Dong Lei <donglei@microsoft.com> Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
Description
clean the code
Task Item
#minor
Screenshots