Skip to content
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

🐛 Bug: Ambassadors Page Not Working Locally #1453

Open
idanidan29 opened this issue Mar 3, 2025 · 3 comments · May be fixed by #1495
Open

🐛 Bug: Ambassadors Page Not Working Locally #1453

idanidan29 opened this issue Mar 3, 2025 · 3 comments · May be fixed by #1495
Assignees
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: In Progress This issue is being worked on, and has someone assigned.

Comments

@idanidan29
Copy link
Contributor

idanidan29 commented Mar 3, 2025

Describe the bug

The Ambassadors page fails to load when running the app locally due to a SyntaxError: Unexpected token '.' in JSON.parse(). The issue appears to be caused by data/ambassadors.json containing a file path instead of valid JSON.

Steps To Reproduce

  1. Run the app locally using yarn run dev .
  2. Navigate to the Ambassadors page (/ambassadors).
  3. See the error in the terminal and browser console.

Expected Behavior

The Ambassadors page should load correctly in the development environment , displaying the list of ambassadors without any JSON parsing errors.

Screenshots

Image

Device Information [optional]

- OS: Windows 11
- Browser: Chrome
- Version: 133.0.6943.127

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

@idanidan29 idanidan29 added Status: Triage This is the initial status for an issue that requires triage. 🐛 Bug Indicates that the issue is a bug or defect. labels Mar 3, 2025
@idanidan29 idanidan29 changed the title 🐛 Bug: 🐛 Bug: Ambassadors Page Not Working Locally Mar 3, 2025
Samarallam97 added a commit to Samarallam97/website that referenced this issue Mar 4, 2025
@Samarallam97
Copy link

I want to work on this issue. Can you assign it to me?

@idanidan29
Copy link
Contributor Author

idanidan29 commented Mar 4, 2025

@Samarallam97 Thank you for your interest in implementing this.

Since I posted the issue, I'd like to be assigned to it. Additionally, I already have the solution.

@benjagm benjagm added Status: Available No one has claimed responsibility for resolving this issue. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. and removed Status: Triage This is the initial status for an issue that requires triage. labels Mar 5, 2025
@benjagm
Copy link
Collaborator

benjagm commented Mar 7, 2025

@idanidan29 go ahead.

@benjagm benjagm added Status: In Progress This issue is being worked on, and has someone assigned. and removed Status: Available No one has claimed responsibility for resolving this issue. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. labels Mar 7, 2025
@idanidan29 idanidan29 linked a pull request Mar 10, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: In Progress This issue is being worked on, and has someone assigned.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants