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

Move all unused functions from catalyst-client to lambdas #1119

Open
menduz opened this issue Jun 4, 2022 · 1 comment
Open

Move all unused functions from catalyst-client to lambdas #1119

menduz opened this issue Jun 4, 2022 · 1 comment
Assignees

Comments

@menduz
Copy link
Member

menduz commented Jun 4, 2022

Many functions present in the catalyst-client are only used by lambdas.

To name a few, we have pipeContent and fetchContentStatus.

In order to provide better APIs for clients, only reused functions should live in the shared client to lower the complexity of the solution and the libraries involved.

@pentreathm pentreathm moved this to Todo in Platform Team Dec 6, 2022
@aleortega aleortega moved this from Todo to In Progress in Platform Team Dec 8, 2022
@aleortega
Copy link
Contributor

These are the functions we need to check:

buildEntity
buildEntityWithoutNewFiles
fetchEntitiesByPointers
fetchEntitiesByIds
fetchEntityById
fetchAuditInfo
fetchContentStatus
downloadContent
isContentAvailable
pipeContent
deployEntity
deploy
getContentUrl

fetchProfiles
fetchWearables
fetchOwnedWearables
fetchOwnedThirdPartyWearables
fetchEmotes
fetchOwnedEmotes
fetchOwnedThirdPartyEmotes
fetchCatalystsApprovedByDAO
fetchLambdasStatus
getLambdasUrl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants