Skip to content
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

Feature/5659 add metadata link #106

Merged
merged 12 commits into from
Aug 6, 2024
Merged

Conversation

HavierD
Copy link
Contributor

@HavierD HavierD commented Jul 31, 2024

No description provided.

@HavierD HavierD requested a review from vietnguyengit July 31, 2024 06:06
@HavierD HavierD marked this pull request as draft July 31, 2024 06:07
@HavierD HavierD marked this pull request as ready for review August 1, 2024 01:53
@@ -19,7 +19,7 @@ const ContactBlock: React.FC<ContactBlockProps> = ({ title, contacts }) => {
key={index}
title={contact.organization + suffix}
isContactFragment
email={contact.emails[0]}
email={contact.emails ? contact.emails[0] : undefined}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no big deal, but what if contact.emails[0] = ""?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If any details is falsy("", undefined, null, etc...), the corresponding area will show something like "no *** data". Steve has this design, but it needed to change according to their discussion. So I will implement all the falsy data when the design is approved. I will then raise a ticket for it (will paste the link here shortly)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -70,7 +89,7 @@ const MetadataInformationPanel = () => {
},
{
title: "Full Metadata Link",
component: <div>full metadata link</div>,
component: <PlainLinkBlock url={metadataLink} />,
Copy link
Contributor

@vietnguyengit vietnguyengit Aug 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so why dont you call PlainLinkBlock to be MetadataLinkBlock? unless plain link block is something called by STAC, I'd suggest a different name for clarity. "Plain" can be replaced by something else / or not needed at all.

import BlockList from "./BlockList";
import { Link } from "@mui/material";

interface PlainLinkBlockProps {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rename @HavierD ?

@HavierD HavierD marked this pull request as draft August 6, 2024 01:28
url: string;
}

const PlainLinkBlock: React.FC<PlainLinkBlockProps> = ({ url }) => {
const LinkList: React.FC<LinkListProps> = ({ url }) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this name can be confusing with https://en.wikipedia.org/wiki/Linked_list

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, sorry. Let me change another one

@@ -20,4 +20,4 @@ const PlainLinkBlock: React.FC<PlainLinkBlockProps> = ({ url }) => {
return <ExpandableList title={"Full Metadata Link"} childrenList={link} />;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you are hard-coded "metadata link" here, so this component is for list of "metadata link" only?

@HavierD HavierD marked this pull request as ready for review August 6, 2024 01:52
@HavierD HavierD requested a review from vietnguyengit August 6, 2024 02:06
@vietnguyengit vietnguyengit merged commit aba5d5e into main Aug 6, 2024
2 checks passed
@HavierD HavierD deleted the feature/5659-add-metadata-link branch August 12, 2024 05:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants