Conversation
Adds a new search page for datasets with active filters, result options and result list item components. Includes creatibutor component for handling both persons and organizations. Includes access status component to display access rights information. Implements a new layout for search apps and adjust existing search components.
Applies theme overrides and adds variables for the RDM (Research Data Management) platform. This includes changes to colors, styles, and layouts for various elements and modules to align with the new design. The changes include: - Adds overrides for collections like tables, grids, and menus. - Adds overrides for elements like buttons, labels, and lists. - Adds overrides for modules like dropdowns and accordions. - Adjusts global styles and variables to ensure consistency across the platform. These changes improve the overall visual appearance and user experience of the RDM platform. Related to FE-430
…rch-stranka-a-vysledky
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 49 out of 60 changed files in this pull request and generated 19 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| } | ||
|
|
||
| .svg-container { | ||
| flex: 0 1 350px;; |
There was a problem hiding this comment.
Extra semicolon after CSS value. Line 21 has flex: 0 1 350px;; with two semicolons. While browsers are generally forgiving, this is invalid CSS syntax and should be fixed:
flex: 0 1 350px;…rch-stranka-a-vysledky
… Creatibutors component
…rch-stranka-a-vysledky
|
Pls rebase this PR, there are many files deleted that shouldn't be deleted (e.g. .variables, .overrides) |
| display: flex; | ||
| flex-direction: column; | ||
| position: fixed; | ||
| bottom: 148px; |
There was a problem hiding this comment.
Use rems or even better vh unit to position on screen
| flex-direction: column; | ||
| position: fixed; | ||
| bottom: 148px; | ||
| right: 44px; |
| } | ||
|
|
||
| @media screen and (max-width: 1679px) { | ||
| bottom: 90px; |
|
|
||
| @media screen and (max-width: 768px) { | ||
| right: 25px; | ||
| bottom: 148px; |
There was a problem hiding this comment.
And here, pixels doesnt work well on devices with various DPI, scaling
| } | ||
| } | ||
|
|
||
| #user-profile-menu.ui.menu { |
|
|
||
| from oarepo_ui.overrides import UIComponentOverride, UIComponent | ||
|
|
||
| OAREPO_UI_OVERRIDES = { |
| @@ -0,0 +1,25 @@ | |||
| <?xml version="1.0" encoding="UTF-8" standalone="no"?> | |||
| @@ -0,0 +1,96 @@ | |||
| import React from "react"; | |||
There was a problem hiding this comment.
Why not use RDM code for this?
There was a problem hiding this comment.
Should be available in app-RDM
There was a problem hiding this comment.
Because I don't like the way it looks by default (roles are missing). Of course I could copy their code, but that is what I did with my previous NMA UI implementation (I copied and modified nr-docs design). The only thing that changes here since previous NMA logic is the metadata model, but the UI design stays the same/similar.
Or since we don't have any usable NMD design, I could of course, copy the whole RDM Search UI, delete all overrides and less and only style colors, etc. (like we did with detail)
| @@ -0,0 +1,50 @@ | |||
| import React from "react"; | |||
There was a problem hiding this comment.
This might not be needed as discussed today
| @@ -0,0 +1,29 @@ | |||
| import React from "react"; | |||
| {i18next.t("Uploaded on")} <span>{createdDate}</span>{" "} | ||
| {version && `(${i18next.t("version")}: ${version})`} | ||
| </> | ||
| {sanitizedDescription && ( |
|
|
||
| return ( | ||
| <Item key={result.id} data-testid="result-item"> | ||
| <Item className="results-list-item-main"> |
| @@ -1,71 +1,188 @@ | |||
| import React from "react"; | |||
| import React, { useContext, useState } from "react"; | |||
There was a problem hiding this comment.
This looks like taken from previous nma, much simpler would be to copy from RDM result item & adapt it to design as it expects RDM model we use now
| const SortLabelMobile = (cmp) => cmp; | ||
|
|
||
| export const ResultOptions = ({ currentResultsState = {} }) => { | ||
| const { total } = currentResultsState.data; |
There was a problem hiding this comment.
Are we 100% sure this cannot happen? Will break whole search ui otherwise
| </Accordion> | ||
| )} | ||
| {orgCreatibutors.length > 0 && ( | ||
| <Accordion style={personalCreatibutors.length > 0 ? { marginTop: "-1rem" } : {}}> |
There was a problem hiding this comment.
No fixed inline styles, conditionally add rel-mt-1 class instead
| ); | ||
| }; | ||
|
|
||
| CreatibutorsList.propTypes = { |
There was a problem hiding this comment.
Creatibutors are solved in RDM (uses the same record model as current nma), can be taken & adapted from there
| ? creatibutor.role.title | ||
| : (creatibutor?.role?.title?.["en"] || | ||
| creatibutor?.role?.title?.["cs"] || | ||
| creatibutor?.role?.title_l10n || |
There was a problem hiding this comment.
Title l10n should be the first option (already localized by backend)
| return person.name || familyName || givenName || ""; | ||
| }; | ||
|
|
||
| const normalizeIdentifier = (identifier) => { |
There was a problem hiding this comment.
This should be handled by backend in ui serialization
| @@ -0,0 +1,96 @@ | |||
| import React from "react"; | |||
There was a problem hiding this comment.
Should be available in app-RDM
…rch-stranka-a-vysledky
|
To answer previous feedback comments and to continue with this one, I have a general question about the Search UI design. What I've done here is that I coppied everything I deemed necessary from previous NMA along with model changes and removed some unnecessary stuff. But from what I understand from feedback I could also only use RDM components and not do any changes here, like we did with detail. I made a PoC of Search UI using only RDM component with minor changes. The goal, as I understood from the feedback comments by @mirekys was to minimize code (if that is our objective). The design along with minimized code can be seen here: #88 |
|




Applies theme overrides and adds variables for the RDM (Research Data Management) platform. This includes changes to colors, styles, and layouts for various elements and modules to align with the new design.
The changes include:
These changes improve the overall visual appearance and user experience of the RDM platform.