Skip to content

[crashtracker] rationalize config/metadata structs in API #556

Open

Description

          So, I don't think this needs to be addressed by this PR (or ever), but it's somewhat weird to me this "config"/"receiver_config"/"metadata" split right now.

All three are always required to be provided by the caller, so it's kinda weird that the caller needs to know about three different types, which end up just being different kinds of configuration.

Originally posted by @ivoanjo in #551 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions