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

Remove relationship event attribute key prefix #300

Closed
leobragaz opened this issue Oct 14, 2020 · 0 comments · Fixed by #302
Closed

Remove relationship event attribute key prefix #300

leobragaz opened this issue Oct 14, 2020 · 0 comments · Fixed by #302
Assignees
Labels
kind/enhancement Enhance an already existing feature; no "New feature" to add
Milestone

Comments

@leobragaz
Copy link
Contributor

As we are doing for the user_block event attribute key prefix, we can also remove the relationship's one.

{
  "type": "relationship_created",
  "attributes": [
    {
      "key": "relationship_sender",
      "value": "desmos1ht80gzw6fz6335uzsjdct6dc566aufv24quvtp"
    },
    {
      "key": "relationship_receiver",
      "value": "desmos1w7h4qvk2w50zy6wj9wuscwrvvj4jv7jtdyaqzz"
    },
    {
      "key": "relationship_subspace",
      "value": "4e188d9c17150037d5199bbdb91ae1eb2a78a15aca04cb35530cccb81494b36e"
    }
  ]
}

Basically we only need to remove relationship_ prefix.

@leobragaz leobragaz added the kind/new-feature Propose the addition of a new feature that does not yet exist label Oct 14, 2020
@leobragaz leobragaz self-assigned this Oct 14, 2020
@leobragaz leobragaz added kind/enhancement Enhance an already existing feature; no "New feature" to add module/relationships and removed kind/new-feature Propose the addition of a new feature that does not yet exist labels Oct 14, 2020
@RiccardoM RiccardoM added this to the v0.13.0 milestone Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhance an already existing feature; no "New feature" to add
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants