@:jsxStatic: add field for identifying jsxStatic components

[kLabz]

Allows identification of a component as a @:jsxStatic component outside the jsx(' ... ') macro, by adding a __jsxStatic:CreateElementType static field to classes with @:jsxStatic meta.

Example usage:

private abstract BundledComponent(Class<ReactComponent>) {
	// ...

	@:to
	public function toCreateElementType():CreateElementType {
		if (untyped this.__jsxStatic != null)
			return untyped this.__jsxStatic;

		return this;
	}
}

[elsassph]

Why the global build macro?

[kLabz]

Because I have no other way to add a build macro to a class with @:jsxStatic meta, since this is not a ReactComponent class.

[elsassph]

Isn't @:jsxStatic supposed to be used only on React classes normally?

[kLabz]

No, it's supposed to be used on non-React classes to make them work like React classes in the jsx context (but without the component lifecycle).

[elsassph]

Ah... you want to solve cases where the class is never used with JSX... eh I don't like that :( but I guess there's no clean solution for that.

[elsassph]

We can avoid calling getBuildFields and return null if we don't need to modify the fields. What would Tink do? ;)

[kLabz]

I always forget about this :)

[kLabz]

And now the cost is almost null, it takes 0.015s on my 1.4s build.

[elsassph]

Can it really be null?

[kLabz]

Since it's a build macro called for every type, yes.

[kLabz]

you want to solve cases where the class is never used with JSX

Not exactly. It doesn't change anything if the class has been used or not with jsx, it's handled there but not modified. I want to solve cases where the class is used outside JSX, whether or not it is used with JSX elsewhere in the project.

This could even (not 100% about that) be built into CreateElementType if we change it into an abstract, so that @:jsxStatic is handled everywhere we use CreateElementType (React.createElement(), HOC functions, etc.).