DUB ignore subConfiguration

[Kozzi11]

problematic dub.json

{
    "name": "fwb",
    "description": "A simple vibe.d server application.",
    "copyright": "Copyright © 2015, jin",
    "authors": [
        "jin",
        "Sönke Ludwig"
    ],
    "dependencies": {
        "vibe-d:core": "~>0.8.0-beta.3",
	"vibe-d:inet": "~>0.8.0-beta.3",
        "vibe-d:data": "~>0.8.0-beta.3",
        "vibe-d:web": "~>0.8.0-beta.3",
        "vibe-d:mongodb": "~>0.8.0-beta.3"
    },
    "versions": [
        "VibeDefaultMain",
        "VibeManualMemoryManagement"
    ],
    "subConfiguration": {
        "vibe-d:core": "vibe-core"
    },
    "targetType": "executable",
    "sourcePaths": [],
    "configurations": [
        {
            "name": "mongodb",
            "mainSourceFile": "source/mongodb.d"
        }
    ]
}

problem is with subConfiguration which is not taken into account, when I try dub build
it still select vibe-d:core with libevent configuration instead of vibe-core.

Only way how to avoid this is to remove all others configurations from vibe-d:core or edit vibe-d:inet and add something like this to inet dub (in sdl format obviosly ):

"subConfiguration": {
        "vibe-d:core": "vibe-core"
}

[s-ludwig]

It's "subConfigurations". There really needs to be a warning for unknown fields!

[Kozzi11]

Wow, so it is subConfigurations in json and it is subConfiguration in sdl? Why?

[wilzbach]

Wow, so it is subConfigurations in json and it is subConfiguration in sdl? Why?

In Sdl it's a single entry, whereas in Json you provide the entire dictionary in one entry.
The also logically applies for example for dependency (sdl) and dependencies (Json).

[Kozzi11]

Oh I see now, I really should stick on sdl and get rid of json

[wilzbach]

Oh I see now, I really should stick on sdl and get rid of json

Yeah, but unfortunately this is unlikely to happen for the general public:

#789

[Kozzi11]

closing this, because it was a typo on my part

[Kozzi11]

thanks @s-ludwig and @wilzbach