How macros use 'MemberMacro' to generate dynamic new methods/properties

In the interface file, if the method signatures added by 'MemberMacro' are not fixed, what should I do? In previous versions, I could declare it like in the diagram, but it's no longer allowed in the latest version. Is there any new approach?

I think I've found the reason; adding `` in the new version of the interface causes an error.