-
Notifications
You must be signed in to change notification settings - Fork 3.2k
feat(ingest): change asset list #14073
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
Conversation
🔴 Meticulous spotted visual differences in 195 of 1548 screens tested: view and approve differences detected. Meticulous evaluated ~9 hours of user flows against your PR. Last updated for commit def23d7. This comment will update as new commits are pushed. |
Bundle ReportChanges will increase total bundle size by 6.49kB (0.03%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: datahub-react-web-esmAssets Changed:
Files in
|
datahub-web-react/src/app/ingestV2/source/__tests__/tests_utils.test.tsx
Show resolved
Hide resolved
9580144
to
f1975fa
Compare
Codecov ReportAttention: Patch coverage is ❌ Unsupported file formatUpload processing failed due to unsupported file format. Please review the parser error message:
|
<div | ||
ref={tabsContainerRef} | ||
style={{ | ||
maxHeight, | ||
overflowY: 'auto' as const, | ||
height: '100%', | ||
position: 'relative', | ||
}} | ||
> | ||
{tabsContent} |
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.
my initial reaction is that adding in refs and scrollTo actions into the Tabs component is not ideal. Generally using refs and scrollTo is a break-glass last approach. If anything, I would have the alchemy component export its ref and do the scrollTo outside unless we're sure this is something we want to bake into all tabs.
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.
If I take this out then I have to break the abstraction of Tabs as finding the correct element to scroll from inside the component was proving to be quite difficult. I did that earlier but then as it was breaking abstraction I opted to do this.
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.
Imo this is ok to do in the component, especially since it's flagged
datahub-web-react/src/app/ingestV2/executions/components/ExecutionDetailsModal.tsx
Outdated
Show resolved
Hide resolved
datahub-web-react/src/app/ingestV2/executions/components/ExecutionDetailsModal.tsx
Outdated
Show resolved
Hide resolved
datahub-web-react/src/app/ingestV2/executions/components/ExecutionDetailsModal.tsx
Outdated
Show resolved
Hide resolved
@gabe-lyons it will look like this in case of more than few types Loom showing the changes https://www.loom.com/share/ed028af28e6a40608fe6edf7348545bd |
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.
Really nice job on your first frontend PR (I think? At least when formally on a product team)! I have one request around handling type unsafety that I'd like to discuss before approval, and a bunch of non-blocking style nits
datahub-web-react/src/alchemy-components/components/Tabs/Tabs.tsx
Outdated
Show resolved
Hide resolved
<div | ||
ref={tabsContainerRef} | ||
style={{ | ||
maxHeight, | ||
overflowY: 'auto' as const, | ||
height: '100%', | ||
position: 'relative', | ||
}} | ||
> | ||
{tabsContent} |
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.
Imo this is ok to do in the component, especially since it's flagged
datahub-web-react/src/alchemy-components/components/Tabs/Tabs.tsx
Outdated
Show resolved
Hide resolved
`; | ||
|
||
const RecipeSection = styled.div` | ||
border-top: 1px solid ${ANTD_GRAY[4]}; |
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.
ant colors are deprecated, please use one in foundations/colors.ts if possible.
|
||
import { GetIngestionExecutionRequestQuery } from '@graphql/ingestion.generated'; | ||
|
||
const SectionHeader = styled(Typography.Title)` |
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.
This code is reused across each tab and we likely want to keep them consistent across tabs. Perhaps we can consolidate these in a components.tsx
or similar. @chriscollins3456 do we have a convention here?
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.
moved to a common file
datahub-web-react/src/app/ingestV2/executions/components/SummaryTab.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.
I'd still prefer to wrap getIngestionContents
and getOtherIngestionContents
in a try / catch, but approving to unblock. Nice job!
if (!structuredReportObject) { | ||
return null; | ||
} | ||
const aspectsBySubtypes = structuredReportObject.source.report.aspects_by_subtypes; |
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.
could this ever throw an error?
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.
const RecipeSection = styled(SectionBase)``; | ||
|
||
const LogsSection = styled(SectionBase)``; |
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.
why create an empty styled component like this?
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.
I was refactoring, got feedback, cleanup, repeat and this happened. Taken care of in #14167
What it looks like https://www.loom.com/share/ec590878c442471488b84aa0dcbe0bc1