Ruby : Event Manager : Google Civic Information API getting turned down in April 2025

[XAJX179]

Checks

• [X] This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
• [X] I have thoroughly read and understand The Odin Project Contributing Guide
• [ ] Would you like to work on this issue?

Describe your suggestion

issue - Google Civic Information API getting turned down in April 2025... Used in Event Manager Project

link to announcement - https://groups.google.com/g/google-civicinfo-api/c/9fwFn-dhktA other link - https://developers.google.com/civic-information/

Path

Ruby / Rails

Lesson Url

https://www.theodinproject.com/lessons/ruby-event-manager

(Optional) Discord Name

xajx

(Optional) Additional Comments

No response

[wise-king-sullyman]

Thanks for raising this issue!

[github-actions[bot]]

This issue is stale because it has had no activity for the last 30 days.

[github-actions[bot]]

This issue is stale because it has had no activity for the last 30 days.

[XAJX179]

@wise-king-sullyman just a reminder!

[XAJX179]

the representative API is the one that is getting turned down in April to be exact.

the project uses the representativeInfoByAddress method of it like this

legislators = civic_info.representative_info_by_address(
      address: zipcode,
      levels: 'country',
      roles: ['legislatorUpperBody', 'legislatorLowerBody']
    )

[JoshDevHub]

Alright we've come to a decision on this, and we're just going to remove the project. This is being done for a couple of reasons.

1. It's always been a bit of a strange project within the context of our course. It's a code along, and it introduces certain things that learners won't properly explore until much later in the Rails course (ERB and using APIs).
2. Getting it to work without Google's API is going to be more effort than it's worth, especially considering the above point.

With this in mind, a couple of things need to happen:

1. In this repo, there needs to be a PR that moves the lesson's files into the archive/ directory.
2. In the main website repo, there needs to be a PR that removes the lesson from the Ruby course fixture file

Opening this up for contributors. Comment below if you want to be assigned.

[Asartea]

Would be willing to do this

[JoshDevHub]

@Asartea Cool, I'll assign you.

We'll have to merge the main site repo PR first. Otherwise there will be issues with production trying to load a lesson that doesn't exist. (not sure if you've worked with the curriculum fixtures much, so just saying this).

In your PR for the curriculum, be sure to link this issue and #29181. This work will close that issue as a side effect.