Using 'type' as a custom attribute conflicts with Konva internal node type and causes unexpected behavior

[JhonnyCarvajalFE]

I was creating shapes with a custom type attribute and accessing it using node.getAttr('type'). The documentation mentions a getType() method that returns the node’s internal type (e.g., Shape, Group, or Stage), but getAttr('type') appears to return the same value as getType() rather than the custom attribute, which caused unexpected behavior. So I guess type is a lib keyword you cant use as a custom attribute, right?

[lavrton]

This is the code of getAttr method:

  getAttr<AttrConfig extends Config, K extends AnyString<keyof Config>>(
    attr: K
  ): K extends keyof AttrConfig ? AttrConfig[K] : any {
    const method = 'get' + Util._capitalize(attr as string);
    if (Util._isFunction((this as any)[method])) {
      return (this as any)[method]();
    }
    // otherwise get directly
    return this.attrs[attr];
  }

As you can see, node.getAttr('anything') will always call node.getAnything() if such method is available. The workaround is to use a different keyword for your type. While saving custom data into any node is possible, I recommend avoiding it or use clear prefixes, so there are no collusions.