jonsgreen

Payment

here is the User Experience that we are shooting for initially:

1. An owner arrives at /signup.
2. they enter account details and create the account
3. they select a subscription level
4. enter cc information (card#159)
5. they arrive at /new/studio, having bypassed 'choose user type screen'
6. they enter the name and site Id for their studio.

raorao

Any top-level comment on pull request ought be tagged with one of four emojis:

• ❓ for a non-blocking comment that asks for clarification. The pull request author must answer the question before the pull request is merged, but does not have to wait for the comment author to re-review before merging.

• 🎨 for a non-blocking comment that proposes a refactor or cleanup. The pull request author does not have to address the comment for the pull request to merge.

• ⚠️ for a blocking comment that must be addressed before the pull request can merge. The comment's author should leave a Request Changes review, and is responsible for re-reviewing once the pull request author has addressed the issue.

• 😻 for a comment that compliments the author for their work.

lsaville

2023-01-10

Changing to iso 1806 style dates cuz who needs anything else amiright?

DISTINCT ON

DISTINCT ON with ORDER BY acts acts like window functions with ranking/row_number. https://www.youtube.com/watch?v=XuGxGP8quMQ

psql get result file workaround

-- Set the variable "query" to the contents of the sql file
\set query `cat my_rad_query.sql`

ryanflorence

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.