Linkauth wildcard seems to expect a different order of arguments

[joshkauffman]

Arguments are listed as: eosc system linkauth [your account] [code account] [action name] [permission name] [flags] When entering: eosc system linkauth dfusecontent eosio.token "*" active I got this error returned: ERROR: invalid name format for "action name": invalid name, 13 characters maximum

However, when flipping around * and active's placement, it allowed the tx to be tried.

As a second error though, it then returned the error:

      {
        "message": "Required permission cannot be empty",
        "file": "eosio_contract.cpp",
        "line_number": 306,
        "method": "apply_eosio_linkauth"
      },
      {
        "message": "",
        "file": "eosio_contract.cpp",
        "line_number": 346,
        "method": "apply_eosio_linkauth"
      },
      {
        "message": "pending console output: ",
        "file": "apply_context.cpp",
        "line_number": 72,
        "method": "exec_one"
      }

[DenisCarriere]

To add support for linkauth wildcard, simply push blank data for type field.

Example

https://eosq.app/tx/ea37b719d9aee58ece21d8da0596787a4c826564663810058a42e08b5bce36ee

{
   "account": "deweb.eosn",
   "code": "deweb.eosn",
   "requirement": "firebase",
   "type": ""
}