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

hxml tasks don't work if there's no hxml in the project root #296

Closed
back2dos opened this issue Sep 13, 2018 · 2 comments
Closed

hxml tasks don't work if there's no hxml in the project root #296

back2dos opened this issue Sep 13, 2018 · 2 comments

Comments

@back2dos
Copy link

Our project has it's hxmls nested deeply and I've set the haxe.displayConfigurations in the settings.json accordingly. If I have an empty hxml in the project root, the compilation works fine with the "active configuration", but as soon as I remove the file I get:

The haxe task detection didn't contribute a task for the following configuration:
{
    "type": "haxe",
    "args": "active configuration",
    "problemMatcher": [
        "$haxe-absolute",
        "$haxe",
        "$haxe-error",
        "$haxe-trace"
    ],
    "group": {
        "kind": "build",
        "isDefault": true
    }
}
The task will be ignored.
@Gama11
Copy link
Member

Gama11 commented Sep 13, 2018

Hm... I've just tried reproducing this, and this does generally work. However, during this I noticed that this error can happen when vshaxe hasn't been activated yet at the time you try to run the task (e.g. when you reload the window and don't have a .hx file open).

Having a .hxml file in the project's root directory happens to activate vshaxe via the workspaceContains:*.hxml activation event.

@Gama11
Copy link
Member

Gama11 commented Sep 13, 2018

Ah, looks like we need this activation event: microsoft/vscode#27087

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

No branches or pull requests

2 participants