-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add CreatePost lib component #27
Comments
…en using it Issue: Image files aren't being sent from the client to IFPS to Lens in the protocol post I've created a duplicate file of `useCreatePost` called `useCreatePostProposalEdit.coffee` which showcases a proposed metadata addition for tagging candidate assets as per the flow in Signal-K/Silfur#26 Here's the console output for when the post was created on the client: https://lenster.xyz/posts/0xa952-0x06 (comment by `u/parselay.lens`) Other related issues: https://github.com/Signal-K/polygon/issues#:~:text=ago%20by%20Gizmotronn-,Migrate%20Proposal%20board%20from%20Vite%20to%20Next.js,-truffle%2Dganache Signal-K/Silfur#25 Signal-K/Silfur#24 Signal-K/Silfur#22 Signal-K/Silfur#21 Discovered this issue with the thirdweb package: Signal-K/Silfur#12 #9
As seen We now need to create a query to set the maximum width of a post, and also create a method to hide comments (those should show up underneath a post). Based on this behaviour, I'm now expecting that we can add additional metadata tags (as seen in |
New styling issue needs to be referenced in Signal-K/client#9 & Signal-K/client#8 however |
Allow users to create posts on our client.
This will allow us to determine how we attach additional metadata to our publications.
Here's a demo metadata tag:
Potentially, one of the tags could point to the contract → nft id that is being referenced (note that
classificationMetadata
is a custom prop.Linear info:
https://linear.app/star-sailors/issue/WB3-8/add-createpost-lib-component
Id: WB3-8
The text was updated successfully, but these errors were encountered: