Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

423 consider refactoring v2 classnames with parent in the name #462

Conversation

augustjohnson
Copy link
Collaborator

Refactored class names for all v2 objects to show inheritance.
Standardized on "parent" to be the upwards field for all objects.
Refactored set keys to be universally unique, and standardized in format.

Tested by running tests, visiting all endpoints, spot checking items, import/export parity, etc.

@augustjohnson
Copy link
Collaborator Author

Merging in because nobody wants to test this crap :/

@augustjohnson augustjohnson reopened this Jun 1, 2024
@augustjohnson augustjohnson merged commit 8b2888a into staging Jun 1, 2024
6 of 7 checks passed
@augustjohnson augustjohnson deleted the 423-consider-refactoring-v2-classnames-with-parent-in-the-name branch June 1, 2024 17:42
@augustjohnson
Copy link
Collaborator Author

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider refactoring v2 classnames with parent in the name.
1 participant