-
Notifications
You must be signed in to change notification settings - Fork 86
fix: add longitude, latitude, and timezone to RequestData.geo #1777
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
Conversation
✅ Deploy Preview for netlify-plugin-nextjs-nx-monorepo-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for netlify-plugin-nextjs-static-root-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
❌ Deploy Preview for nextjs-plugin-custom-routes-demo failed.
|
✅ Deploy Preview for next-plugin-edge-middleware ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
❌ Deploy Preview for netlify-plugin-nextjs-next-auth-demo failed.
|
❌ Deploy Preview for netlify-plugin-nextjs-export-demo failed.
|
❌ Deploy Preview for next-plugin-canary failed.
|
✅ Deploy Preview for next-i18next-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
❌ Deploy Preview for nextjs-plugin-next-11-demo failed.
|
✅ Deploy Preview for netlify-plugin-nextjs-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
084127f
to
6c44ddc
Compare
745e278
to
9b296f0
Compare
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.
In Netlify context, longitude
and latitude
are of type number
, but Next.js types them as string | undefined
. See https://nextjs.org/docs/api-reference/next/server#nextrequest. I wonder if on our end we should convert them to string to avoid any issues on the Next.js side. I do find it odd that they're not treated as numbers on the Next side though.
9b296f0
to
129a1d1
Compare
129a1d1
to
949689a
Compare
I believe the failures for the checks are Next 11 related. |
2926672
to
4d0801f
Compare
@@ -63,10 +64,13 @@ const handler = async (req: Request, context: Context) => { | |||
return | |||
} | |||
|
|||
const geo = { | |||
const geo: RequestData['geo'] = { |
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.
Yay type!
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.
🎉
There's Next 11 demo sites failing, but just going to see about the other site failures. |
Looks like all things Cypress are passing, so I think all the failures are related to Next 11 tests. |
If you look at details you can see that several demo sites failed to build. I don't think it's the fault of this PR (I think it's npm-related) but Cypress tests alone won't say that everything is passing. |
Are the Cypress tests passing because it's not using the |
Summary
Test plan
Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
Closes https://github.com/netlify/pod-ecosystem-frameworks/issues/305
Relates to https://github.com/netlify/pod-compute/issues/270
Relates to netlify/cli#5231
Standard checks:
🧪 Once merged, make sure to update the version if needed and that it was published correctly.