-
Notifications
You must be signed in to change notification settings - Fork 1
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
Gizmotronn
merged 10 commits into
main
from
wb3-5-take-user-inputs-for-minting-via-flask
Jan 4, 2023
Merged
π¬π€ β New API Routes, #25
Gizmotronn
merged 10 commits into
main
from
wb3-5-take-user-inputs-for-minting-via-flask
Jan 4, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
β¦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
β¦mic routes for profile loading Signal-K/Silfur#24 & #16
β¦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
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
commented
Jan 4, 2023
There was a problem hiding this 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-> #24 by @Gizmotronn
Extras:
#24 -> #18, #16, #6