-
Notifications
You must be signed in to change notification settings - Fork 189
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
Update Feed
in parser
service to talk to Supabase instead of Redis
#3464
Comments
There's also this:
|
I'm working on this issue to make parser save flagged feeds to supabase (simply change
I will also need to change this line if I'm removing all the redis flagging feed code, something like this if (await isFlaggedFeed(feed.id)) // isFlaggedFeed() is function that uses supabase
return; Therefore, the test won't pass and there's no mock cilent for supabase at the moment. I'm not sure what's the next step is |
Mock the |
I'll try, thanks |
After looking at the function telescope/src/api/parser/src/parser.js Lines 12 to 28 in 9ec0cf0
I believe we can keep it as it looks for feed object in Redis not in Supabase. |
In #1907 #3355, we talked about removing feed-related code in Posts.
Change
setInvalidFeed
function to use Supabasetelescope/src/api/parser/src/utils/storage.js
Lines 111 to 115 in d56306a
telescope/src/api/parser/src/utils/storage.js
Lines 137 to 139 in d56306a
The text was updated successfully, but these errors were encountered: