David Humphrey

@joanjeremiah go for it.

The error happens here in the sso service: https://github.com/Seneca-CDOT/telescope/blob/adf299da6e6e9c3f20208ee6ab61d205a9f70eab/src/api/sso/src/routes/logout.js#L22

Looking at this a bit more: We're failing here: https://github.com/Seneca-CDOT/telescope/blob/adf299da6e6e9c3f20208ee6ab61d205a9f70eab/src/api/sso/src/routes/login.js#L33-L36 Which somehow means we're not getting what we expect on the query string here: https://github.com/Seneca-CDOT/telescope/blob/e40693018b5471bd582c78d9889fa3261943d4b6/src/api/sso/src/middleware.js#L74-L77 That's weird, because we have...

Probably adding some kind of URL param to return a fully hydrated object is best (i.e., don't do it unless requested). For example: - `GET /posts` returns `id` and `url`...

Somewhat related, we'll have to figure out if the logic for adding posts needs to stay there, or get moved out to another service too. See #1865.

Given that feeds will live in Supabase, we should probably remove this, yes. It's still needed.

We should figure out what is actually calling the feeds route. I suspect it's the old parser, which is going away. The new parser can talk directly to Supabase (cc...

This can happen post-3.0

@Eakam1007 assigned to you. cc'ing @JerryHue as well for thoughts.

This can happen after 3.0