-
Notifications
You must be signed in to change notification settings - Fork 16
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
NFT Metadata form #2125
NFT Metadata form #2125
Conversation
Your Render PR Server URL is https://chainsafe-components-stage-pr-2125.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-c9tops7s437hl15oop1g. |
Your Render PR Server URL is https://files-ui-stage-pr-2125.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-c9topt7s437hl15oop60. |
Your Render PR Server URL is https://storage-ui-stage-pr-2125.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-c9topu7s437hl15oopng. |
This pull request introduces 3 alerts when merging c44d2cd into 0ae6827 - view on LGTM.com new alerts:
|
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.
Nice!! I left a couple comments in the code, I'll play with it now :)
packages/storage-ui/src/Components/Elements/FormikImageInput.tsx
Outdated
Show resolved
Hide resolved
packages/storage-ui/src/Components/Elements/FormikImageInput.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Thibaut Sardan <33178835+Tbaut@users.noreply.github.com>
This pull request introduces 3 alerts when merging c4f2d21 into 443c575 - view on LGTM.com new alerts:
|
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.
Leaving a couple of comments here.
Looking into the UI.
packages/storage-ui/src/Components/Elements/FormikImageInput.tsx
Outdated
Show resolved
Hide resolved
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.
Played with it locally and all tests passed but one. (the one that's marked as only right now)
files must be a
array
type, but the final value was:null
. If "null" is intended as an empty value be sure to mark the schema as.nullable()
So I fixed this. The yarn
issue was pretty weird, but I'll check it out more in detail if it keeps failing.
edit: I really think that's a red herring for a problem somewhere else. With a git --version
it also fails to find git. But I don't think this is the origin of the problem, why would it appear now anyway.. see https://lifesaver.codes/answer/error-couldn-t-find-the-binary-git-2083
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.
Lets go with it 👍
* bump to v4 * nit to run github actions * with debug and git * with nit * with nit * fix yml * +1 * gooo * fix debug maybe * with nit * double debug * without sudo * yes to all * to all
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.
uuuh yes
This is a very basic MVP of the NFT Metadata creation. The main objective here was to ensure that the basic requirements can be met. The UX can still do with a lot of improvement.
This addresses the initial part of #1931