Separate custom types into its own file and format

[rchl]

No description provided.

[rchl]

Unfortunately there are some annoying

Union syntax cannot be used with string operand; use quotes around entire expression

errors that ruff can't fix automatically and it's hard to make a generic solution for those since the syntax is dependent on context...

[predragnikolic]

Union syntax cannot be used with string operand; use quotes around entire expression

Looks like this error will not happen if we use Union instead of | for the custom.py generated types.

[predragnikolic]

cbf1302
I am fine if the types are not sorted, but rather follow the order in how they are defined in the meta json file. (but ignore this one, as it is not really important)

[rchl]

cbf1302 I am fine if the types are not sorted, but rather follow the order in how they are defined in the meta json file. (but ignore this one, as it is not really important)

I've assumed that order in upstream file could change randomly on update so went with sorting.

Maybe upstream file is updated manually in which case it wouldn't be a problem but I still like sorting anyway (in general) since it's easier to locate stuff.

[rchl]

Hmm, but the generated types that I've included in LSP now don't match those here.

In LSP I've used types after triggering ruff fix and then manually fixing remaining issues.

We could also ignore those issues in LSP but then we'd have to update those again.

But that's probably better than trying to fix the issue here. It will probably solve itself anyway after migrating to 3.14.

[rchl]

I'm OK with this state. If you are too then I will update types in LSP to match those.

[predragnikolic]

It will probably solve itself anyway after migrating to 3.14.

👍

I'm OK with this state. If you are too then I will update types in LSP to match those.

Yes, I think it would be good to also update LSP. (only for consistence)

with future of python we can make adjustments to remove UP006, UP007