Skip to content

Awareness: readback after mutation with no semantic types #310

@jwulf

Description

@jwulf

Logging for future awareness.

While implementing #305, we implemented #309 to allow "readback after mutation" to prove that the mutation held.

Turns out that at least updateUserTask takes no semantic types in the changeset, so these have to be synthesized.

The mutated fields likewise have no semantic types in getUserTask.

So we are correlating them by matching on name.

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