-
Notifications
You must be signed in to change notification settings - Fork 651
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 new fields to metadata modal #5016
Conversation
👍 Looks good to me. |
That icon on the dropdown should be the default one.
|
I can suggest some text for the License field once we know what the icon indicates? Is it a tooltip? It it mandatory? Otherwise, here is my best guess: Additionally, I would keep the field descriptions consistent- either all statements or all questions. Typically, product UI field descriptions are statements so the Source description should say something like "Enter the source of the data" |
Was changed due to a reshuffling in the iconfont contents
Per code review
The icon is a mistake, I suspect the change of the icons recently (should be the default dropdown/chevron icon), fixed now: @csobier It's a standard dropdown (see new screenshot above). It's value is optional (thus the "-" option at the top for, which I was asking if we should replace that with some text instead? Apart from that, updated the placeholders, I'll keep that guideline in mind for the next forms I'll do 👍 |
The margin between the inputs should be the same than between the first and
|
🇪🇸
|
Add new fields to metadata modal
I'll go ahead and merge this, if you want any additional changes just create a new issue and assign me :) |
Fixes #4803
While I didn't have any mockups this time I simply added the new fields between desc and tags, i.e.:
Empty values/placeholders:
Licence dropdown:
@saleiva @josecruz OK? Or did you have another idae on how it should look?
@csobier and @brittanymicek for copy (see the placeholder texts above). also notice the "-" for the non-selected license perhaps we should have some text there instead?
@javierarce can you do the code review, please?