ikappas / vscode-composer Goto Github PK

Hi there,

We decided to remove this extension from the https://github.com/open-vsx/publish-extensions repository, since it has not had any activity for a while and we try to make the list of published extensions shorter.

This means that new versions of the extension will not be available on the OpenVSX registry, but feel free to enable automatic publishing yourselves, we made a pretty easy guide in our repo [1].

Feel free to close this, just wanted to let you know :)

Why there is always need of composer.workingPath. Can't we autodetect those file :)

The problem

I tried to start composer via the command option composer init, but nothing happened, i.e., the file composer.json wasn't created.

Step-by-step what I have done:

Step 1:

Step 2:

I pressed the key Enter, then... nothing at all on explorer...

Informations:

O.S.: popOS 22,04 LTS
VS Code: 1.69.0 (x64)

Furthermore, I have configured the composer path correctly.

{
	"composer.executablePath": "/usr/local/bin/composer"
}

The Composer: Run Script works flawlessly but you need to type the script name every time. It'd be nice if it could auto-detect available scripts and either expose them as commands:

Composer: Run Script → start
Composer: Run Script → build
Composer: Run Script → …

… or feed them to some drop-down list or auto-completion thingie.

You can get a script list with composer run-script --list or parsing composer.json.

Hi,

1. I haven't specified anything under the "composer.workingPath" option, and yet, when composer is called, the "--working-dir" option gets added. That's a first unexpected behavior.

2. This becomes a real problem if the directory has spaces, which isn't handled gracefully as seen is the screenshot below. I suppose adding quotes around here should do the trick ?

   vscode-composer/src/composer/extension.ts

   Line 556 in f0e5684

   commandArgs.push('--working-dir', context.workingPath);

Regards,

Nicolas

In the Disabling Packagist.org section of the Composer documentation, it's specified that the following can be used in the "repositories" section.

    {
        "packagist.org": false
    }

However, when using this extension, the previous snippet causes two "Missing property" problems; one for "type" and the other for "url". I attempted to locate the JSON schema used in this extension with no luck. I'm not sure how validation of the composer.json file is performed, however this does need to be corrected.

It would be great if there was an configuration option to set additional command line arguments. I have an package that only works on linux (vend/resque) because it requires ext-pcntl, and composer isn't able to complete successfully without adding in an "--ignore-platform-reqs" on Windows (See composer/composer#4584). I am currently running updates by hand to get around this issue.

Thanks.

Set default composer executable path.

It must be composer in all systems, and composer must be available in path.

I'm a VS Codium user, a FLOSS version of VS Code, it's the same code but without the Microsoft's telemetry and branding.
I want to request if possible to add the Composer extension on the open-vsx.org market to us doesn't need to works with the Microsoft marketplace as is unclear if it's legal to use it on VS Code forks, see here.

Additional info:

• This is how to publish a new extension.

It seems that a new release (implementing #20 which fixes #19) is still missing right now (cf. #19 (comment) and #20 (comment)). Apparently, the develop branch has not been merged with the master branch.

🤔

At this time, the most recent release available on Visual Studio Marketplace is still 0.7.1 (dated from 12 Nov 2017) and not any automatted update is detected.

Therefore, the error below always recurs when using the extension:

Unable to load schema from 'http://json.schemastore.org/composer': Request vscode/content failed unexpectedly without providing any details.

Forwarded from microsoft/vscode#126699

Issue Type: Bug

When creating a new composer.json file, the JSON extension fails to validate with the following message:
{
"resource": "/Users/pedro/Projects/sql-updates/composer.json",
"owner": "generated_diagnostic_collection_name#0",
"code": "768",
"severity": 4,
"message": "Problems loading reference 'http://json.schemastore.org/composer': Unable to load schema from 'http://json.schemastore.org/composer': Request vscode/content failed unexpectedly without providing any details.",
"startLineNumber": 1,
"startColumn": 1,
"endLineNumber": 1,
"endColumn": 2
}
Navigating to that URL directly shows the following error:
"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

The schema validates correctly per "composer validate" command.

What does exactly the command Composer:Require? via command line, I set composer require vendor/package but not else via VSCode command interface.

Whenever I run Composer Update, I get the following in my VSCodeTerminal:

Executing: composer install

Command completed with errors.

I manually downloaded the schema.json, added it as schema to my composer as:

"$schema": "../schema.json",

As the requested url will show a page with the message that the file was moved.
original url: http://json.schemastore.org/composer
new URL - downloaded: https://raw.githubusercontent.com/composer/composer/master/res/composer-schema.json

It is the first time for me working with VSCode and composers, I think I am missing something fundamentally.

I added the zipfile of the project ( from a udemy course, so should be correct ) that I want to compose.
MadelineprotoWithMysql.zip

How can I debug the situation or what do I have to do in order to get this resolved?

Issue Type: Bug

Extension version: 0.7.1
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 6.1.7601

Would be great if you could integrate a version lookup when editing composer.json (like what happens in package.json) or when using this extension.

will be great to add a config option for changing the composer working directory to an arbitrary folder

It would be great addition if we could ctrl+click on a dependency inside composer.json and directly focus the sidebar to the relative package in vendors directory.

Hi,

i tried this extension to run https://github.com/wudi/swoole-ide-helper, but i had no success. I do not understand how to use the vendor folder all in all correctly, and so got no autocompletition. How does vs code use this files?

Can you help me how to use this?