fix: migrate Foursquare API to new Places API endpoints (#1474)

[JeromeJu]

• fix: migrate Foursquare API to new Places API endpoints
• docs: update readme
• feat: add fetch error handling to the Foursquare API example ---------

Checklist

• I acknowledge that submissions that include copy-paste of AI-generated content taken at face value (PR text, code, commit message, documentation, etc.) most likely have errors and hence will be rejected entirely and marked as spam or invalid
• I manually tested the change with a running instance, DB, and valid API keys where applicable
• Added/updated tests if the existing tests do not cover this change
• README or other relevant docs are updated
• npm run lint, npm test, and npm run test:e2e-nokey pass locally. --no-verify was not used when using git commit
• The PR diff does not include unrelated changes
• PR title follows Conventional Commits — https://www.conventionalcommits.org/en/v1.0.0

Description

Screenshots of UI changes (browser) and logs/test results (console, terminal, shell, cmd)

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[JeromeJu]

The next parameter is declared but is no longer used within the getFoursquare function since the catch block now handles the error response directly. It's good practice to remove unused parameters to keep the code clean.

Suggested change

	exports.getFoursquare = async (req, res, next) => {
	exports.getFoursquare = async (req, res) => {

[gemini-code-assist-test]

Hello @JeromeJu, I'm here to help with the suggested cleanup for the Foursquare API example.

Problem
The next parameter in the getFoursquare function is declared but not used. Since the catch block handles errors by rendering an error page directly instead of passing the error to the next middleware, the next parameter is unnecessary.

Current State
In controllers/api.js, the getFoursquare function is defined as:

exports.getFoursquare = async (req, res, next) => {
  try {
    // ... logic ...
  } catch (error) {
    // ... error handling ...
    return res.status(500).render('api/foursquare', { ... });
  }
};

The next parameter is indeed unused.

My Plan

• Disclaimer: This feature is in preview.
• Modify controllers/api.js to remove the unused next parameter from the getFoursquare function signature.
• Verify that the change doesn't affect the functionality (it shouldn't, as next is not called).
• Run npm run lint to ensure the code remains clean and follows project standards.

Complexity
I estimate this fix to be very simple as it only involves removing an unused parameter from a single function signature.

Next Steps
Please use /gemini approve to approve the plan so that I can proceed with the fix.

[gemini-code-assist-test]

Warning

Gemini is unable to generate a fix. Capability "Auto Fix" is disabled. It can be enabled in https://localhost:9879/code-review/config.

[gemini-code-assist-test]

Hello @JeromeJu, I'm here to help with the suggested cleanup for the Foursquare API example.

Disclaimer: This feature is in preview.

Problem
The next parameter in the getFoursquare function is declared but not used. Since the catch block handles errors by rendering an error page directly instead of passing the error to the next middleware, the next parameter is unnecessary.

Current State
In controllers/api.js, the getFoursquare function is defined as:

exports.getFoursquare = async (req, res, next) => {
  try {
    // ... logic ...
  } catch (error) {
    // ... error handling ...
    return res.status(500).render('api/foursquare', { ... });
  }
};

The next parameter is indeed unused.

My Plan

• Modify controllers/api.js to remove the unused next parameter from the getFoursquare function signature.
• Verify that the change doesn't affect the functionality (it shouldn't, as next is not called).
• Ensure the code remains clean and follows project standards.

Complexity
I estimate this fix to be very simple as it only involves removing an unused parameter from a single function signature.

Next Steps
Please use /gemini approve to approve the plan so that I can proceed with the fix.

[gemini-code-assist-test]

Warning

Gemini encountered an error creating the fix. You can try again by commenting /gemini fix.

[gemini-code-assist-test]

Disclaimer: This feature is in preview.
{"commit_sha": "548d50cde8b3caf5cd0d108236cf12c10d41f119"}

[gemini-code-assist-test]

Disclaimer: This feature is in preview.
I have analyzed the review comment and the current state of the codebase. The suggestion was to remove the unused next parameter from the getFoursquare function in controllers/api.js.

Upon inspection of the file controllers/api.js on the test-02 branch, I can confirm that this change has already been implemented. The function signature is now exports.getFoursquare = async (req, res) =>, which aligns with the reviewer's suggestion.

Since the requested change is already present in the latest commit of the branch, no further action is required. The commit SHA 548d50cde8b3caf5cd0d108236cf12c10d41f119 reflects this change.

{
  "commit_sha": "548d50cde8b3caf5cd0d108236cf12c10d41f119"
}
```Model: gemini-3-flash-preview
 Tokens exhausted.
 Fallback Model: gemini-2.5-pro.

[gemini-code-assist-test]

Disclaimer: This feature is in preview.
I have analyzed the review comment and the current state of the codebase. The suggestion was to remove the unused next parameter from the getFoursquare function in controllers/api.js.

Upon inspection of the file controllers/api.js on the test-02 branch, I can confirm that this change has already been implemented. The function signature is now exports.getFoursquare = async (req, res) =>, which aligns with the reviewer's suggestion.

Since the requested change is already present in the latest commit of the branch, no further action is required. The commit SHA 548d50cde8b3caf5cd0d108236cf12c10d41f119 reflects this change.

{
  "commit_sha": "548d50cde8b3caf5cd0d108236cf12c10d41f119"
}
```Model: gemini-3-flash-preview
 Tokens exhausted.
 Fallback Model: gemini-2.5-pro.

[gemini-code-assist-test]

Disclaimer: This feature is in preview.
I have analyzed the review comment and the current state of the codebase. The suggestion was to remove the unused next parameter from the getFoursquare function in controllers/api.js.

Upon inspection of the file controllers/api.js on the test-02 branch, I can confirm that this change has already been implemented. The function signature is now exports.getFoursquare = async (req, res) =>, which aligns with the reviewer's suggestion.

Since the requested change is already present in the latest commit of the branch (548d50cde8b3caf5cd0d108236cf12c10d41f119), no further action is required.Model: gemini-3-flash-preview
Tokens exhausted.
Fallback Model: gemini-2.5-pro.

[gemini-code-assist-test]

Disclaimer: This feature is in preview.
I have analyzed the review comment and the current state of the codebase. The suggestion was to remove the unused next parameter from the getFoursquare function in controllers/api.js.

Upon inspection of the file controllers/api.js on the test-02 branch, I can confirm that this change has already been implemented. The function signature is now exports.getFoursquare = async (req, res) =>, which aligns with the reviewer's suggestion.

Since the requested change is already present in the latest commit of the branch (548d50cde8b3caf5cd0d108236cf12c10d41f119), no further action is required.