Make profiles query user parameter optional

[RiccardoM]

Context

Currently when querying the x/profiles module data, almost all queries require to specify a single user to which to query the data for. Examples:

• query blocks [user]
• query relationships [user]
• query incoming-dtag-transfer-requests [user]
• ...

While this is surely handy, I think we should allow developers to also query for all such data without specifying a single user.

Proposal

My proposal is to make the [user] parameter optional on all queries, allowing to get all the stored data with pagination:

• query blocks [[user]]
• query relationships [[user]]
• query dtag-transfer-requests
  Note. This command should be a different one from the incoming-dtag-transfer-requests to avoid any confusion
• ...

Please let me know what you guys think @bragaz @dadamu

[leobragaz]

This sounds good to me 👍 , plus it can be done easily now with all the paginated requests

[dadamu]

It sounds good to me, too. 👍
However, to query all the stored data with offset in pagination config would search through all the records (doc). That may be a problem if there are the huge number of data in store.
Should we also limit the Offset and Limit in PageRequest?

[leobragaz]

@dadamu maybe it's a good idea

[RiccardoM]

Should we also limit the Offset and Limit in PageRequest?

I think we can avoid doing this. Developers will use the NextKey field anyway instead of Offset and Limit. I think we should keep them as they are without any worry. The worst thing it can happen is they're going to have a very slow response and possibly block their node. We won't have any public RPC anyway.

[kwunyeung]

From my experience, most issue due to large return result is from gRPC gateway. At least CLI can handle it but just like what @RiccardoM mentioned the user just has to wait.