Comment 4 for bug 1597603

Speaking from the user perspective, it took me a while to even understand what snapcraft was doing. I definitely expected the file name and the plugin name to match, which seems like the straightforward choice. Anything else is magic that needs to be understood.

Speaking from the designing perspective, point (1) above (from Kyle) is a bug IMO. If there is a local plugin named x-foo, it should be respected at all times, even if there's a standard plugin named foo. That's in fact the only reason it'd make sense to name the plugin with the x- prefix. If we implement an order of precedence, then the developer would have everything with the same name and not bother about introducing a disambiguation prefix.