Skip to content

Mapped proposal_states table to middle layer as enum

Sam Kagan requested to merge map-proposal-state-to-middle-layer-as-enum into main

It's called ProposalStateEnum.

Also:

  • Removed ProposalState class since it's no longer necessary for constraining Prop.state in the ORM

Open question: Where should we deal with the conversion of In Review to InReview? In this MR I do it both from db -> middle_layer and middle_layer -> FE. I think the first of these is unnecessary, and we should say that db enums should never contain whitespace so that they can be mapped more easily to Python enums. What do y'all think?

Edited by Sam Kagan

Merge request reports