In MetacatUI, we have a lot of nested types that are defined in a parent type. For example, MapConfig has a nested type CameraPosition. Currently, we use # to separate the parent type and the nested type, like MapConfig#CameraPosition. However, this syntax is not supported in all cases with ESLint. The issue entails switching to the @namespace tag to define nested types (as cleverly suggested by @yvonnesjy).
The syntax namespace#nestedType is allowed when defining @typedefs, but not when defining @propertys or @params. However, we need to be able to refer to these custom types in all cases.
In MetacatUI, we have a lot of nested types that are defined in a parent type. For example,
MapConfig
has a nested typeCameraPosition
. Currently, we use#
to separate the parent type and the nested type, likeMapConfig#CameraPosition
. However, this syntax is not supported in all cases with ESLint. The issue entails switching to the@namespace
tag to define nested types (as cleverly suggested by @yvonnesjy).The syntax
namespace#nestedType
is allowed when defining@typedef
s, but not when defining@property
s or@param
s. However, we need to be able to refer to these custom types in all cases.See:
@namespace
tag documentationjsdoc/valid-types
rule documentation