Skip to content

Tracking issue: move views and params out of common #388

@david-crespo

Description

@david-crespo

This is meant to capture the substantial followup work based on #369, #374, and #386.

Now that we have generated clients for internal communication, each app should own the structs that define its request bodies (params) and responses (views). The difficulty is that there are a lot of changes to be made before we reach the desired end state, way more than would be reasonable to put in a single PR. Refactors should be done as quickly as possible, but there's going to be a short time where we're in an intermediate state. Also doing a bunch of refactors while we're all hurrying for Milestone 3 is not a good idea. So we're going to have to finish this afterward.

This is not a complete list, I'll add more as I go through them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions