-
Notifications
You must be signed in to change notification settings - Fork 143
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
fix(aws): add missing base path to data routes #672
fix(aws): add missing base path to data routes #672
Conversation
🦋 Changeset detectedLatest commit: 57f4814 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Unit tests should work again. I guess you could have one inside here:
|
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.
No unit test run just fine.
In packages/tests-unit
just run pnpm run dev
.
You'll have to add a test here
describe("fixDataPage", () => { |
NextConfig.skipTrailingSlashRedirect = true; |
commit: |
Added two tests. Test suite seems to run successfully. Let me know if those are redundant, or you'd rather me add the base path to existing tests instead. I'm happy to update it as you see fit. |
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.
https://github.com/opennextjs/opennextjs-aws/actions/runs/12284689715/job/34281243192?pr=672
Run pnpm biome check --fix
at the root of the repo
Looks like it failed on write permission reporting the test coverage in |
So weird, a test started failing locally for some reason now. |
@alebelcor I think the reset are done on each describe, not on each test inside describe |
if you add this under line 471 it seems to work here. might be that the global beforeEach(()=> {
NextConfig.basePath = undefined;
}) |
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, thanks!
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 Thanks
Related #670
I was trying to figure out how to add (and run) a unit test in
matcher.test.ts
but then I saw this issue that mentions all unit tests are broken (?).If e2e test(s) are required I'd appreciate any help as I'm not very familiar. And let me know if you need something else.
Thanks!