Following up on previous AST related issues.
I still found some constructs where the range of the attributes is not included in the parent node in signature files.

namespace SomeNamespace

[<Foo1>] // SynModuleSigDecl.Types / SynTypeDefnSig
type MyType =
    class
    end

type FooType =
    [<Foo2>] // ValSpfn
    abstract x : int

See AST Viewer

Expected behaviour

Attributes are included.

Actual behaviour

They are not.

Known workarounds

Parse the tree to construct a correct range.

Related information

FCS 39.