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

Fix annoying popup error. #51

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Rodrigo-Barros
Copy link

Hello from Brazil.

Hey I see that someone started a feature to debug trace messages between vscode and phpactor language server but was not in the client code, so I opened this pull request.

What this feature do is: control the popup terminal window show, based on value of phpactor.trace.server.vebosity.
Captura de tela de 2023-04-30 21-23-23

set "off" for phpactor.trace.server do not popup the terminal window when a request fail.

Note: I update the version in package.json and I add mkdir to help automatically create the artifacts folder too.


I have one doubt. I run the phpactor via socket in a virtual machine running Linux, and accessed via socket on windows machine everything worked as expected, but only for tag 0.18.1. This is supposed to be happen or is something related to current refactoring.

@dantleech
Copy link
Contributor

I have one doubt. I run the phpactor via socket in a virtual machine running Linux, and accessed via socket on windows machine everything worked as expected, but only for tag 0.18.1. This is supposed to be happen or is something related to current refactoring.

i'm not sure -- what happens that is not as expected? is it a separate issue?

let trace = {
"off" : RevealOutputChannelOn.Never,
"message" : RevealOutputChannelOn.Warn,
"verbose" : RevealOutputChannelOn.Info
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this the same feature? is there some documentation / comparable language server extension to compare with?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dantleech
Copy link
Contributor

dantleech commented May 1, 2023

also maybe the confusion is because the settings for phpactor.trace.server in package.json is automatically used by vscode - and controls if code will verbosely log the communication between client and server... it doesn't need any corresponding code in the extension itself.. perhaps there is another setting for revealing the window on error.

... although also good to report the error that is being triggered so it can be fixed :)

@Rodrigo-Barros
Copy link
Author

is this the same feature? is there some documentation / comparable language server extension to compare with?

Yes is the same feature, sorry if I misunderstand.

also maybe the confusion is because the settings for phpactor.trace.server in package.json is automatically used by vscode

I don't knew it.

i'm not sure -- what happens that is not as expected? is it a separate issue?

Yes it is. I wiil open a issue to not blend the subjects.

Thank you for your time.

@dantleech
Copy link
Contributor

dantleech commented May 1, 2023

Yes is the same feature, sorry if I misunderstand.

I mean.. why should the trace verbosity affect if the output channel is revealed? what makes you think this is how it should be done?

@Rodrigo-Barros
Copy link
Author

Yes is the same feature, sorry if I misunderstand.

I mean.. why should the trace verbosity affect if the output channel is revealed? what makes you think this is how it should be done?

Hi again, I think must have an option to disable the annoying error pop up, even if another json key must be created only for that. In debug scenarios this could be enabled or maybe set the default value to show the popup, but could be disabled by the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants