[tcgc] Should we support body nested path/query/header params cases?

[MaryGao]

The @body would ignore any inner path/query/header decorators, so these kinds of spec may not be our good practice. My question is if we need to support these cases and if not supported should we report errors in tcgc directly?

playground

op foo(@body body: Test):void;

model Test {
  @path
  prop1: string;

  @query
  prop2: string;

  @header
  prop3: string;
}

[timotheeguerin]

Why not, why do you this differently than not having those decorator is the question. Gethttpoperstion for example shouldn’t list those as header, query, etc