powerbackme / powerback Goto Github PK

This should be corrected to only show "first" for the truly chronologically first Celebration, otherwise say "one."

Relevant code:
Explore.tsx

type-route is the app's router dependency.

As a Single Page Application, back and forward browser navigation must be virtualized to maintain a native feel for the user.

The algorithm in app.js works fine when navigating the mobile Login landing screen, however copies of the instance in the user's browser history of visiting the app begin to fill up, meaning lots of clicking for the user if they want to "get out."

Customer_id is a property under Stripe's Payment API.

When verifying a payment method, the app sends a request to Stripe for this value. However, a user is free to navigate backward in the process, eventually bringing themselves back at some point to requesting the Customer_id, which happens each time a user breaks and returns to the process.

Instead, it might be better to store Customer_id somehow, if not with Stripe directly, then in the database or other storage.

relevant code:
components/forms/Payment/Payment.tsx
routes/api/payments.js
controller/payments/
models/User.js

Winston is the app's backend logging dependency.

Usage of Winston should be configured to properly log backend activity.

Changing user settings should immediately alter the UI environment based on any related changes.

frontend

• /Settings
• /AccountModal
• src/.../updateUser.js
• API.ts

backend

• routes/../users.js
• update.js

In the CheckoutCard component there is a submit ("Confirm") button element from Stripe positioned under the credit card number input element. If using a keyboard to tab into focusing on this element, it becomes stuck, so the keyboard becomes useless to navigate elsewhere on the page.

Related code:
Payment.tsx

The Celebrations component contains a Vertical Timeline that maps the Celebration Event component.

Celebrations uses React Suspense with a Placeholder as a fallback.

If possible, it would be better to always render a parent component which contains placeholder elements "threaded" in with the real sub-elements that make up the Event component, instead of doing an either-or type render with the fallback placeholder or the fully rendered content.

This is because when the fallback changes to the rendered content, the Vertical Timeline has a "bounce-in" animation that is triggered a second time. A smoother effect would have this bounce only once on a parent element.