[Bug]: Parsing decorators and directives for Namespaces

[tjprescott]

Discussed in #3164

^{Originally posted by tjprescott April 12, 2024}

#suppress "deprecated"
@TypeSpec.service( { title: "Test", version: "1" } )
namespace Azure.Test {  
  #suppress "foo" "bar"
  @doc("SubNamespace")
  namespace SubNamespace {
    model Blah {
      name: string;
    }      
  }
}

When I examine the type graph nodes:

• Namespace SubNamespace has one decorator and one directive.
• Namespace Test only has one decorator and no directives. I would expect it to have one directive and one decorator.

As it turns out, but examining the parent of Test, which is Azure I then observe:

• Namespace SubNamespace has one decorator and one directive.
• Namespace Test only has one decorator and no directives.
• Namespace Azure only has one directive and no decorators.

Given that these are both written in the same way, I would expect both the directive and the decorator to be located on the node for the Test namespace.

Is there a reason they are treated differently? This seems like a bug to me. I can track back through parents, but then (as expected) I end up getting duplicate directives.