-
Notifications
You must be signed in to change notification settings - Fork 1
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
eventPassCardFooter: add next intl provider for EventPassContractReve… #271
Conversation
…alContractButton and mock next/cache for test in updateEventPassCart EventPasses.tsx and PasCardSelect.tsx : added NextIntlProvider migration: change order_amount_handling to not count quantity on update payment-admin: integration tests to make sure stripeCheckoutSession is deleted if the execution of the function goes right updateEventPassCart: change migration to not count existing pendingOrder quantity in total quantity and added tests for those edge cases cart/purchase : reason in search params stripe process: add button and action to cancel a purchase order and a stripe session, added tests for the getStripeActiveCheckoutSession function and especially the no user/user mail case lowercase for all eth addresses : update tests and add migration for the insert trigger ; make the cancel my purchase button reactive
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
PR Description updated to latest commit (f1b7855) |
PR Analysis
PR Feedback💡 General suggestions: The changes introduced in this PR seem to be well thought out and are likely to enhance the functionality of the application. However, it would be beneficial to ensure that all changes are thoroughly tested, especially those related to the handling of Ethereum addresses and the stripe process. Additionally, it would be helpful to include more detailed comments in the code to explain the purpose and functionality of the new features and changes. ✨ Usage guide:Overview:
With a configuration file, use the following template:
See the review usage page for a comprehensive guide on using this tool. |
… the component doesn't render when there is no file
…e internal translations
hasura/app/migrations/default/1707365734019_insert_lowercase_trigger/up.sql
Outdated
Show resolved
Hide resolved
...tures/back-office/events/src/lib/molecules/EventPassFilesUploader/EventPassFilesUploader.tsx
Show resolved
Hide resolved
const router = useRouter(); | ||
const [value, setValue] = useState( | ||
boundedNumericStepperProps.initialValue || 0, | ||
); | ||
const { toast } = useToast(); | ||
const t = useTranslations('Organizer.Event.PassPurchase'); | ||
|
||
return ( | ||
<BoundedNumericStepper |
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.
Would be better to use a revalidateTag on the action (to avoid weird UX on the Sheet and intercepted route so pass purchase card version), instead of router.refresh, if nextjs is not buggy as it used to with 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.
Without the router.refresh on the first completion of the onChange function, it seems to switch to the /purchase instead of staying on the sheet .purchase, could be a revalidateTag causing a reload and eventually loading the /purchase because of the URL
…ts for the action
@@ -29,7 +29,7 @@ export interface EventPassFilesTableProps | |||
buttonClassName?: string; | |||
} | |||
|
|||
export function EventPassFilesUploader(props: EventPassFilesTableProps) { | |||
export async function EventPassFilesUploader(props: EventPassFilesTableProps) { |
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.
Well no the issue here really is the 'use server';
at the top of the file that should be removed.
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.
That way in the client context it's going to be a client component and on the server side a RSC. If it works ?
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.
Oh no you are right, we are using getTranslations
from server so never mind
@@ -1,3 +1,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.
We need to give a name after the unix timestamp that say shortly what's the migration about
@@ -29,7 +29,7 @@ export interface EventPassFilesTableProps | |||
buttonClassName?: string; | |||
} | |||
|
|||
export function EventPassFilesUploader(props: EventPassFilesTableProps) { | |||
export async function EventPassFilesUploader(props: EventPassFilesTableProps) { |
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.
That way in the client context it's going to be a client component and on the server side a RSC. If it works ?
@@ -29,7 +29,7 @@ export interface EventPassFilesTableProps | |||
buttonClassName?: string; | |||
} | |||
|
|||
export function EventPassFilesUploader(props: EventPassFilesTableProps) { | |||
export async function EventPassFilesUploader(props: EventPassFilesTableProps) { |
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.
Oh no you are right, we are using getTranslations
from server so never mind
User description
…alContractButton and mock next/cache for test in updateEventPassCart
EventPasses.tsx and PasCardSelect.tsx : added NextIntlProvider
migration: change order_amount_handling to not count quantity on update
payment-admin: integration tests to make sure stripeCheckoutSession is deleted if the execution of the function goes right
updateEventPassCart: change migration to not count existing pendingOrder quantity in total quantity and added tests for those edge cases
cart/purchase : reason in search params
stripe process: add button and action to cancel a purchase order and a stripe session, added tests for the getStripeActiveCheckoutSession function and especially the no user/user mail case
lowercase for all eth addresses : update tests and add migration for the insert trigger ; make the cancel my purchase button reactive
Type
Enhancement
Changes walkthrough
17 files
nftActivity.integration.test.ts
Update
fromAddress
andtoAddress
to use lowercase addresses innftActivity.integration.test.ts
libs/indexer/alchemy/webhooks/src/lib/nftActivity.integration.test.ts
fromAddress
andtoAddress
values in themockActivity
andmockActivity2
objects to use lowercase addresses.packCollection.integration.test.ts
Update
contractAddress
to use lowercase addresses inpackCollection.integration.test.ts
libs/nft/thirdweb-organizer/src/packCollection.integration.test.ts
contractAddress
values in themockActivity
andmockActivity2
objects to use lowercase addresses.pendingOrder.spec.ts
Add
eventPass3
and test case for updating order with new quantity inpendingOrder.spec.ts
libs/gql/user/api/src/queries/cart/pendingOrder.spec.ts
eventPass3
object with a lowercasecontractAddress
value.that exceeds the max limit.
payment-admin.integration.test.ts
Add integration tests for
confirmedStripeCheckoutSession
inpayment-admin.integration.test.ts
libs/payment/admin/src/lib/payment-admin.integration.test.ts
confirmedStripeCheckoutSession
function.
BoundedNumericStepper.tsx
Refactor
BoundedNumericStepper
to usevalue
prop andonChange
callbackin
BoundedNumericStepper.tsx
libs/ui/components/src/lib/bounded-numeric-stepper/BoundedNumericStepper.tsx
useState
hook and replaced it with avalue
prop andonChange
callback.increment
anddecrement
functions to use thevalue
propand
onChange
callback.UserCart.tsx
Add `reason` prop and section to `UserCart` in `UserCart.tsx`
libs/features/cart/src/lib/UserCart/UserCart.tsx
reason
toUserCartProps
andUserCart
component.UserCart
to display an alert ifreason
prop isprovided.
PassCardSelect.tsx
Add `value` prop to `PassCardSelect` in `PassCardSelect.tsx`
libs/features/organizer/event/src/lib/molecules/PassCard/PassCardSelect.tsx
value
toPassCardSelectProps
andPassCardSelectContent
component.PassCardSelectContent
component to use thevalue
prop.PassPurchaseHeader.tsx
Add
CancelPurchaseButton
component toPassPurchaseHeader
inPassPurchaseHeader.tsx
libs/features/organizer/event/src/lib/molecules/PassPurchaseHeader/PassPurchaseHeader.tsx
CancelPurchaseButton
to handle canceling apurchase order.
PurchaseInProgressAlert
component to include theCancelPurchaseButton
.CancelPurchaseButtonClient.tsx
Add
CancelPurchaseButton
component to handle canceling a purchaseorder in
CancelPurchaseButtonClient.tsx
libs/features/organizer/event/src/lib/molecules/PassPurchaseHeader/CancelPurchaseButtonClient.tsx
CancelPurchaseButton
to handle canceling apurchase order.
CartCancelled.stories.tsx
Add story for
CartCancelled
component with cancel purchase button inCartCancelled.stories.tsx
libs/features/cart/src/lib/CartCancelled/CartCancelled.stories.tsx
CartCancelled
component with cancel purchasebutton.
action.ts
Add
cancelPurchaseForUser
function to handle canceling a purchaseorder in
action.ts
libs/features/organizer/event/src/lib/molecules/PassPurchaseHeader/action.ts
cancelPurchaseForUser
to handle canceling apurchase order.
getStripeActiveCheckoutSession.ts
Update
getStripeActiveCheckoutSession
to throw error if user has noemail in
getStripeActiveCheckoutSession.ts
libs/features/payment-api/src/lib/getStripeActiveCheckoutSession.ts
getStripeActiveCheckoutSession
function to throw an errorif the user has no email.
updateEventPassCart.ts
Update
updateEventPassCart
to revalidate tags inupdateEventPassCart.ts
libs/features/organizer/event-actions/src/lib/updateEventPassCart.ts
updateEventPassCart
function to revalidate tags even whenrunning in Jest.
PassPurchase.stories.tsx
Update
WithPurchaseInProcess
story to include cancel purchase buttonin
PassPurchase.stories.tsx
libs/features/organizer/event/src/lib/pages/PassPurchase/PassPurchase.stories.tsx
WithPurchaseInProcess
story to include the cancel purchasebutton.
EventPassNftFilesTableClient.tsx
Return
null
ifdata
array is empty inEventPassNftFilesTableClient.tsx
libs/features/back-office/events/src/lib/molecules/EventPassNftFilesTable/EventPassNftFilesTableClient.tsx
null
if thedata
array is empty.EventPassCardFooter.tsx
Replace `_locale` with `locale` in `EventPassCardFooter.tsx`
libs/features/back-office/events/src/lib/molecules/EventPassCardFooter/EventPassCardFooter.tsx
_locale
variable and replaced it withlocale
variable.getStripeActiveCheckoutSession.spec.ts
Add unit tests for
getStripeActiveCheckoutSession
ingetStripeActiveCheckoutSession.spec.ts
libs/features/payment-api/src/lib/getStripeActiveCheckoutSession.spec.ts
getStripeActiveCheckoutSession
function.✨ Usage guide:
Overview:
The
describe
tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.When commenting, to edit configurations related to the describe tool (
pr_description
section), use the following template:With a configuration file, use the following template:
Enabling\disabling automation
meaning the
describe
tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.the tool will replace every marker of the form
pr_agent:marker_name
in the PR description with the relevant content, wheremarker_name
is one of the following:type
: the PR type.summary
: the PR summary.walkthrough
: the PR walkthrough.Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.
Custom labels
The default labels of the
describe
tool are quite generic: [Bug fix
,Tests
,Enhancement
,Documentation
,Other
].If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:
Main topic:performance
- pr_agent:The main topic of this PR is performanceNew endpoint
- pr_agent:A new endpoint was added in this PRSQL query
- pr_agent:A new SQL query was added in this PRDockerfile changes
- pr_agent:The PR contains changes in the DockerfileThe list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.
Inline File Walkthrough 💎
For enhanced user experience, the
describe
tool can add file summaries directly to the "Files changed" tab in the PR page.This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set
pr_description.inline_file_summary
in the configuration file, possible values are:'table'
: File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.true
: A collapsable file comment with changes title and a changes summary for each file in the PR.false
(default): File changes walkthrough will be added only to the "Conversation" tab.Utilizing extra instructions
The
describe
tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.
More PR-Agent commands
See the describe usage page for a comprehensive guide on using this tool.