-
Notifications
You must be signed in to change notification settings - Fork 78
[AUCT-744] iOS request condition report #2050
Conversation
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.
So far so good 👍 I think @dblandin might want to review this PR as well since he just worked on a similar change in Reaction artsy/reaction#3099 and I see a lot of similar bits of code here.
Let me know if you need help for writing tests.
Remove redundant condition section Test artwork details condition section Remove unused context module in schema
…uest Allow modifying textAlign in Modal, center aligning lot condition request Remove unused import
Workaround for modal layout issues, tests for feature flag, see details Workaround modal top margin affecting layout Undo accidental padding change in modal Fix test add feature flag disabled test Type assertion as string for other list items
Alright this is finally ready for review:
Corresponding PR in reaction: Successfully requesting a condition reportError on requesting a condition reportNotes:
|
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.
So good! 🙌 Amazing job on the tests ✨
Had one question about the circle config file, and then a few smaller suggestions but overall I really appreciate how thorough and clear this code is ❤️
Use optional chaining for lab option Remove unused mutationMessage param, cleanup promise completion Add explicit type to state Consolidate loading state updates
@@ -58,4 +59,89 @@ describe("Artwork Details", () => { | |||
expect(component.text()).not.toContain("Frame") | |||
expect(component.text()).not.toContain("Signature") | |||
}) | |||
|
|||
it("shows condition description if present and not biddable", () => { | |||
const artworkDetailsInfo = { |
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.
minor: but is it possible to provide a type to this fixture? I think we would want to type with RequestConditionReport_artwork
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.
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 added a type for the fixtures, good idea! Here the type is ArtworkDetails_artwork
and there isn't a test query (I didn't write this original test). However I am happy to refactor to use a test query if you want just let me know.
Use passed in relay environment Use passed in relay environment Updates tests with new relay prop Typifying artwork in artworkDetails tests Add relay prop to analytics tests
src/lib/Scenes/Artwork/Components/__tests__/RequestConditionReport-analytics-tests.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.
LGTM - merge at your discretion
Type safety in requestCondition report tests Add return type in requestConditionReport promise
🚀 PR was released in v1.21.40 🚀 |
I don't think I can finish this PR this week, so I'm hoping @erikdstock or @yuki24 can take it over.