Escaping parameter names and values fails

[w-vi]

Following APIB produces warning on the first parameter
warning: (3) unable to parse additional parameter traits, expected '([required | optional], [<type> | enum[<type>])', e.g. '(optional, string)'; line 8, column 7 - line 8, column 38

If the escaping takes place on the parameter name as well as example value it fails.

# A

## A [/a{?u_u,u}]

### Get A [GET]

+ Parameters 
    + `u_u` (required, string, `a_a`)
    + u (required, string, `a_a`)

+ Response 200

CURRENT WORKAROUND
Use different syntax for the example:

    + `u_u`: `a_a` (required, string)

[pksunkara]

Old parameter format doesn't support escaping for the parameter name. This is intentional.

[w-vi]

Huh, what? Why? Is it documented somewhere? I haven't found it.

[pksunkara]

Old parameter format is not an MSON format. Escaping as a concept only exists in MSON. Old parameter format is deprecated currently.

[w-vi]

I see, so we should issue deprecation warning I suppose as this is confusing.

[pksunkara]

We currently support both formats albeit one of them without being the spec. MSON parameters and headers RFC should take care of this later.

I am closing this for now.

[w-vi]

This is not solved really, as it is nowhere to be seen that I am using deprecated feature.

[pksunkara]

It is not deprecated yet. But there is no mention of the old format anywhere in the spec.

[w-vi]

So lets clarify it somehow (spec, docs, warning) and then we can close it.