Minimize camel case headaches

[jsstevenson]

Feature description

We should figure out ways to minimize headaches regarding translation between snake case (python norm) and camel case (GKS naming standards)

Use case

Fusion-Curation uses a TS-ified version of the FUSOR models to construct fusion objects client-side in camel case, but then has to translate the highest property keys to snake case to use the FUSOR constructors. Those constructors then convert keys back to camel case to actually construct the objects. This is annoying.

Proposed solution

I don't think there's an end-all solution here, but one option is to add alias generators to all FUSOR models.

Alternatives considered

No response

Implementation details

No response

Potential Impact

No response

Additional context

No response

Contribution

Yes, I can create a PR for this feature.

[github-actions]

This issue is stale because it has been open 180 days with no activity. This issue will be closed if no further activity occurs in 14 days.