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

Allow absolute config paths #11

Closed
wants to merge 2 commits into from
Closed

Allow absolute config paths #11

wants to merge 2 commits into from

Conversation

Ilyes512
Copy link

I tried using this plugin with "Remote Containers"-extension without success. It couldn't find the psalm.xml file. The file was not in the root of the workspaceFolder but one down (in ${workspaceFolder}/src).

Even after setting psalm.configPaths I couldn't get it to work. After a few hours of digging I finally got it running by allowing setting absolute paths to the config (it will try the path as given without prefixing it with the workspaceFolderPath).

I also set the extensionKind to workspace. It basically means that it wants to be where the workspace (vscode-server) is installed instead of on the UI-side. More info here: doc.

More info on Remote Containers here: docs.

@pristinesource pristinesource added the enhancement New feature or request label Apr 21, 2020
@pristinesource
Copy link
Collaborator

@Ilyes512 I like the changes, but we had to merge some other stuff in and it looks like it caused a merge conflict. Do you think you could pull in the latest changes in master and apply your update again? Thanks!

@Ilyes512
Copy link
Author

Well, it would have been nice to merge PR's in historical order and more so if the MR that caused the merge conflict was yours. I guess it was a nicer feature to have.

I will update this MR soon and let you know.

@muglug
Copy link
Member

muglug commented May 6, 2020

I will update this MR soon and let you know.

Thanks, and sorry for my out-of-order merging

@tm1000 tm1000 self-requested a review June 29, 2021 00:59
@tm1000 tm1000 changed the base branch from master to feature/2.x June 29, 2021 01:23
@tm1000 tm1000 mentioned this pull request Jun 29, 2021
17 tasks
@tm1000
Copy link
Collaborator

tm1000 commented Aug 2, 2021

I've ended up resolving this in a different way in the 2.x release since everything depends on the workspace you are in

@tm1000 tm1000 closed this Aug 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants