You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to that, for reusable enum generation (which would fix generating tons of exactly-the-same-not-compatible-with-eachother-enums on frontend), we need to add enumName property to ApiProperty. I think we can do it now fairly easily, because the name of enums could match import exactly. Otherwise, on every route there's a new enum and its literally unusable
p.s. I wonder what should I do to contribute? What's the process? @Brakebein
The text was updated successfully, but these errors were encountered:
According to that, for reusable enum generation (which would fix generating tons of exactly-the-same-not-compatible-with-eachother-enums on frontend), we need to add
enumName
property toApiProperty
. I think we can do it now fairly easily, because the name of enums could match import exactly. Otherwise, on every route there's a new enum and its literally unusablep.s. I wonder what should I do to contribute? What's the process? @Brakebein
The text was updated successfully, but these errors were encountered: