Feature: validator claim query

[zacck-zz]

Changes Proposed

• Collect all claims for a validator
• Expose query to fetch claims
• Ensure to collect only claims I can vote or I have voted on

[zacck-zz]

@alissonfpmorais I think that should make it work, please see if it agrees with yours

[alissonfpmorais]

@alissonfpmorais I think that should make it work, please see if it agrees with yours

Hey @zacck I've tested and now looks like that the query return the correct claim, but before merge it, I would like to know from you @zacck and @lucca65 how we gonna use those queries.

The dashboard also needs data related to community (symbol and logo related to each claim) and objective (id, also related to each claim). In that case the frontend will do multiples queries and then join all the results?
The same happens to verification screen, not only we need community and objective data, but, in case of multiples queries, we also need a way to get an specific entry of objective and claim.

Is this right? What you folks think about that?

[lucca65]

yeah this is a possibility, but we can also query several different queries on GraphQL, no need to actually do different queries, for example:

query {
  x: community(symbol:"BES") {
    description
  }
  y: community(symbol:"LOR") {
    description
  }
}

Maybe to improve this conversation, can you please send me the graphql query to the claims, and we can create a new one that contemplates the community queries as well so you get descriptions, logo and symbols to your heart's contents

[zacck-zz]

@alissonfpmorais @lucca65 with a couple of modifications to our Schema,

That is, adding the objective association to an action and community association to an objective we can pick this data entirely from the claims query as follows

query ($input: ClaimsInput!) {
  claims(input: $input) {
    id
    action {
      objective {
         id
        community {
          symbol
          logo
        }
      }
    }
  }
}

[alissonfpmorais]

@alissonfpmorais @lucca65 with a couple of modifications to our Schema,

That is, adding the objective association to an action and community association to an objective we can pick this data entirely from the claims query as follows

query ($input: ClaimsInput!) {
  claims(input: $input) {
    id
    action {
      objective {
         id
        community {
          symbol
          logo
        }
      }
    }
  }
}

@zacck Really cool dude, like it a lot!!

One more thing is that we also need a way to get a specific verification for the verification screen.

Maybe something like?

query($input: ClaimInput!) { // with ClaimInput being claim ID and the validator who is requiring the claim (so you can check if that validator can verify that claim or not)
  claim(input: $input) {
     // data needed
  }
}

[zacck-zz]

@alissonfpmorais I can do the query you need (claim(claim_input)) however I don't see the need to require the validator since the backend doesn't need to know about permissions really and the front end will have the validator id which it can tell from eos whether they can verify or not ... what do you think

[alissonfpmorais]

@alissonfpmorais I can do the query you need (claim(claim_input)) however I don't see the need to require the validator since the backend doesn't need to know about permissions really and the front end will have the validator id which it can tell from eos whether they can verify or not ... what do you think

Yeah, since I've those data I can check it on frontend.
Makes sense! It's fine for me dude

[zacck-zz]

@alissonfpmorais done 👍