You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The curent implementation #479 list all the chains without any filtering.
I don’t think it will be good in a UX point of view since spn has the potential to store many chain. We have pagination capability for the query but I don’t think it is useful for this case.
We should have some kind of filtering. I think the most obvious filter we have is the source of the chain. A user interested in a project may want to know all the chains being deployed from that project.
So we could have an option —[source|project] fadeev/venus that list of the chains of this project. (It could even be mandatory in my opinion).
If this is implemented, we should also do refacto in spn to index the chains from their sourceURL.
The text was updated successfully, but these errors were encountered:
The curent implementation #479 list all the chains without any filtering.
I don’t think it will be good in a UX point of view since
spn
has the potential to store many chain. We have pagination capability for the query but I don’t think it is useful for this case.We should have some kind of filtering. I think the most obvious filter we have is the source of the chain. A user interested in a project may want to know all the chains being deployed from that project.
So we could have an option
—[source|project] fadeev/venus
that list of the chains of this project. (It could even be mandatory in my opinion).If this is implemented, we should also do refacto in
spn
to index the chains from their sourceURL.The text was updated successfully, but these errors were encountered: