Conversation
✅ Deploy Preview for veda-ui ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
e2213db to
838976d
Compare
e0fdd52 to
22e18f9
Compare
22e18f9 to
368e455
Compare
There was a problem hiding this comment.
Looking great! Love the attention to details like the collapsible search field on mobile 🥳
A bunch of things:
- I had to uncomment the
thematicsfield in the urban heating dataset for this to run. - (nit) cursor on the featured datasets card's thematic pill is reverting to the 'move' cursor on hover, and it has a hover style (while not clickable) which is a bit confusing. Also because it's not clickable, I'd give it a disabled style especially since the pills on the non featured cards are clickable.
- Clicking on the card's thematic pills should scroll up to the filters bar IMHO.
- Make search case-insensitive ('Car' yields results, 'car' does not)
- We probably don't need the card's top right 'DATASET' pill
- (nice-to-have) Also perform a search on thematic areas ('eis' in the search box should filter datasets with eis thematic)
- (nice-to-have) On the dataset count block:
'Showing 2 datasets out of 45 clear filters' or 'Showing all 45 datasets'
|
|
||
| interface CardComponentProps { | ||
| title: string; | ||
| title: React.ReactNode; |
There was a problem hiding this comment.
Just out of curiosity: do we have a set practice on using React types directly, rather than importing them (import React, { ReactNode } from 'react';)
There was a problem hiding this comment.
I don't think we do. Do you favor one?
There was a problem hiding this comment.
We usually import everything at the top of a file, so for consistency's sake, I don't see why this should be different for React types (especially in this file where we have 4 occurrences). Very much nitpicking though.
| const { topic, source, sortField, sortDir, onAction } = controlVars; | ||
| const search = controlVars.search ?? ''; | ||
|
|
||
| const displayDatasets = prepareDatasets(allDatasets, { |
|
Thank you for the very thorough review @nerik! 🙏 Some notes on your points:
I made the thematics optional for now, but should they be required on every dataset?
Pill now behaves like any other text. I decided not to disabled it running the risk of making it too invisible. @ricardoduplos, any concerns on this point?
Great idea! Done.
Done
There are places where there is related data (like discoveries) and the cards show up. That pill is the way to tell them apart. To be consistent it is also shown here. I think @ricardoduplos was rethinking that, but maybe for later.
Wouldn't this make the filter redundant? Or is this good redundancy? @ricardoduplos thoughts?
Implemented. @ricardoduplos to comment on design.
@ricardoduplos Would the UI library form field hint work here? |
|
Thanks for addressing the feedback, and sorry for not commenting in-context, this makes things messy.
I'm not sure but ideally, we'd have an explicit
Also deferring to @ricardoduplos - if we leave it I'd recommend disabling the hover styles similar to what you did for the thematic pills. |
|
@nerik @ricardoduplos Addressed all the items we discussed. :) See commits above |
|
@karitotp This is ready to undergo some QA testing. |

Implement Data Catalog page according with the mockups (#484)
By SOURCEand the source filter only has theAlloptions (More info on Implement data catalog new page (filtering / search) #511 )