-
Notifications
You must be signed in to change notification settings - Fork 2
messages for platform winding down, updates to payments buttons to support free content for all content but still track payments #85
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| # Repository Guidelines | ||
|
|
||
| ## Project Structure & Module Organization | ||
| The Next.js app lives in `src/`, with page routes in `src/pages`, reusable UI in `src/components`, hooks in `src/hooks`, shared helpers in `src/utils`, and server-facing logic under `src/lib` and `src/db`. Context providers, constants, and config live in `src/context`, `src/constants`, and `src/config`. Styling combines Tailwind layers and globals in `src/styles`, while static files sit in `public/`. Database schemas and migrations are managed via `prisma/schema.prisma` and `prisma/migrations/`. Local infrastructure relies on `docker-compose.yml` and the project `Dockerfile` for Postgres-backed workflows. | ||
|
|
||
| ## Build, Test, and Development Commands | ||
| Install dependencies once with `npm install`. Use `npm run dev` for the hot-reloading Next.js server, or `docker compose up --build` when the Postgres service is required. Apply schema updates with `npx prisma migrate dev` and regenerate clients via `npx prisma generate` (also run automatically on `postinstall`). Before shipping, execute `npm run build` followed by `npm run start` to verify the production bundle. Guard code quality with `npm run lint`, and auto-fix common issues using `npm run lint:fix`. | ||
|
|
||
| ## Coding Style & Naming Conventions | ||
| Prettier enforces two-space indentation, single quotes, trailing commas (ES5), and 100-character lines; run it before committing. Favor functional React components with PascalCase filenames such as `src/components/ProfileCard.tsx`. Keep hooks prefixed with `use`, colocate utility modules near their feature, and import shared modules with the `@/` path alias defined in `jsconfig.json`. | ||
|
|
||
| ## Testing Guidelines | ||
| A formal automated test suite is not yet established. Treat linting and targeted manual verification as the baseline, and capture edge cases in your PR description. When adding tests, colocate them beside the feature as `feature.test.ts(x)` files or place them in a nearby `__tests__/` folder. Always rerun `npm run lint` and any affected flows locally before requesting review. | ||
|
|
||
| ## Commit & Pull Request Guidelines | ||
| Write concise, imperative commit subjects (e.g., `Add wallet connect modal`) and group related changes together. Pull requests should restate the problem, highlight key updates, link relevant issues, and include screenshots or short clips for UI adjustments. Confirm that `npm run lint`, schema migrations, and regeneration steps have been executed, and call out required environment variables such as `.env.local` entries. | ||
|
|
||
| ## Environment & Security Notes | ||
| Request secrets from maintainers rather than reusing staging values. Never commit credentials or Prisma client artifacts unless schema changes demand it. Mask sensitive values—especially `POSTGRES_PRISMA_URL` and `POSTGRES_URL_NON_POOLING`—in logs and PR discussions, and review `.github/workflows/` when introducing automation to keep credentials scoped. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Bug: Promo Pricing Overwrites Discount Codes
The new promo pricing logic (lines 83-87) bypasses existing discount code functionality, leading to a confusing UX where discounts appear applied but are ignored. This also removes the check for 0-satoshi discounted amounts, which could cause issues when fetching invoices if a discount would make the course free.