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

πŸ”¬πŸ€ ↝ New API Routes, #25

Merged
merged 10 commits into from
Jan 4, 2023

Conversation

Gizmotronn
Copy link
Member

@Gizmotronn Gizmotronn commented Jan 4, 2023

Some minor styling changes...
Idea for metadata: Create an nft with all the contents of the candidate, then edit them to include some actions the player did on the candidate, then send that lazy-minted NFT as the metadata/publication contents for the Lens post.
This way we can have a frontend like on the client dir example & automate the process of creating & updating the metadata & candidate content on the nft using Flask & Jupyter (see next commit for some more info)
Done some minor fetching examples, this seems to be causing some console issues on next in Server/frontend so will attempt to fix those later as well

-> #24 by @Gizmotronn

Extras:

#24 -> #18, #16, #6

Gizmotronn and others added 10 commits December 23, 2022 02:00
…board-from-vite-to

πŸ§–πŸ»β€β™‚οΈπŸ“Š ↣ Failure to migrate from Vite to Next
…n-using-moralis

πŸŒ’β™»οΈ ↝ Flask, Lens, Moralis authentication + Read/Write, graphql interactivity
#16 , Signal-K/Silfur#24
…n-using-moralis

πŸ‰β›‘οΈ ↝ Base structure for new gql queries for Lens
Currently there's a mutate issue in `lib/auth/useLogin.ts` (in `Server/frontend`). (not assignable to param type ~~...). This is causing the SignInButton (which is derived from @thirdweb-dev/react (sdk) to also have an error with the default return statement (which should provide an access token from Lens IF the user has succesfully connected their wallet, completed a challenge (this challenge will later be replaced by the Flask-based challenge in `Server/app.py`), and signed in with Lens. So I'll be fixing this in the next commit.

More notes available on the Notion page linked in #23 / #22 / #21
…d (and defining some new roles for #16 backend)

Check out the Notion documentation here: https://skinetics.notion.site/Lens-posting-a07f0e9c243249c0a3517e4160874137

Currently having a bit of a problem with determining the method we'll use to define proposal parameters, but I've come up with a fallback solution (i.e. using bots & comments) for the MVP. Potentially these "comments" could also be stored off-Lens but still be visible on the frontend (problem here is if you're looking at the proposals from an alternate client), bringing the Discord integration further into the limelight (using DeWork.xyz as the intermediary bot), as well as highlighting a real usecase/benefit to having both Supabase & Moralis as the data stores. Hopefully the metadata standards for publications are just as loose as with the `appId` standard on lens, as we'll just be able to create dummy metadata that is saved to the IPFS publication URI and therefore callable via graphql.

So overall, a lot of questions coming up, but some UI improvements as well as some more read interactivity for the client...
…w flask route #16 to fetch proposal data

Some minor styling changes...

Idea for metadata: Create an nft with all the contents of the candidate, then edit them to include some actions the player did on the candidate, then send that lazy-minted NFT as the metadata/publication contents for the Lens post.

This way we can have a frontend like on the `client` dir example & automate the process of creating & updating the metadata & candidate content on the nft using Flask & Jupyter (see next commit for some more info)

Done some minor fetching examples, this seems to be causing some console issues on next in `Server/frontend` so will attempt to fix those later as well
…-using-moralis

πŸ”­πŸ”¬ ↝ Additional read functions for Lens, plus some new Flask content
@Gizmotronn Gizmotronn added documentation Improvements or additions to documentation duplicate This issue or pull request already exists enhancement New feature or request data source data source for content generation in [HDASH-4] goerli Issues relating to the ethereum components of Star Sailors, e.g. NFT, Moralis/Supabase labels Jan 4, 2023
@Gizmotronn Gizmotronn self-assigned this Jan 4, 2023
Copy link
Member Author

@Gizmotronn Gizmotronn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data source data source for content generation in [HDASH-4] documentation Improvements or additions to documentation duplicate This issue or pull request already exists enhancement New feature or request goerli Issues relating to the ethereum components of Star Sailors, e.g. NFT, Moralis/Supabase
Projects
Development

Successfully merging this pull request may close these issues.

1 participant