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

GitHub extension: refresh on settings change #29556

Closed
bpasero opened this issue Jun 27, 2017 · 5 comments
Closed

GitHub extension: refresh on settings change #29556

bpasero opened this issue Jun 27, 2017 · 5 comments
Assignees
Labels
*not-reproducible Issue cannot be reproduced by VS Code Team member as described

Comments

@bpasero
Copy link
Member

bpasero commented Jun 27, 2017

Testing: #29507

When changing the settings (username) I suggest to refresh the view of issues automatically.

@chrmarti chrmarti added this to the June 2017 milestone Jun 27, 2017
@chrmarti
Copy link
Collaborator

I have a listener registered and that seems to work. The only case I can reproduce this is when the user setting goes from a non-null value to null. In that case no event is fired. Could this be related to changes you recently made @sandy081 ?

@sandy081
Copy link
Member

Will check

@chrmarti
Copy link
Collaborator

There have been other fixes that might have improved the experience. Reassigning to you @sandy081 for the remaining one.

@chrmarti chrmarti assigned sandy081 and unassigned chrmarti Jun 29, 2017
@sandy081
Copy link
Member

sandy081 commented Jun 30, 2017

@chrmarti I see the event when the user setting goes from a non-null value to null. Please see the attached video. In the extension, I am listening to configuration change and logging the values of github section and it works as expected

kapture 2017-06-30 at 8 35 10

Here is my code in extension

export function activate(context: vscode.ExtensionContext) {
	vscode.workspace.onDidChangeConfiguration(() => {
		console.log(vscode.workspace.getConfiguration('github'));
	});
}

Are there any other steps to reproduce this?

@sandy081 sandy081 assigned chrmarti and unassigned sandy081 Jun 30, 2017
@chrmarti chrmarti removed this from the June 2017 milestone Jun 30, 2017
@chrmarti chrmarti added the *not-reproducible Issue cannot be reproduced by VS Code Team member as described label Jun 30, 2017
@chrmarti
Copy link
Collaborator

Ack, it now works. Guess it must have been fixed. Thanks!

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*not-reproducible Issue cannot be reproduced by VS Code Team member as described
Projects
None yet
Development

No branches or pull requests

3 participants