Skip to content

fix: don't use cached results for linkedin when triggered from mp 🧹#873

Merged
ramiAbdou merged 1 commit into
mainfrom
rami/debug
Aug 22, 2025
Merged

fix: don't use cached results for linkedin when triggered from mp 🧹#873
ramiAbdou merged 1 commit into
mainfrom
rami/debug

Conversation

@ramiAbdou
Copy link
Copy Markdown
Member

Description ✏️

This PR updates the caching logic for fetching a LinkedIn profile. When triggered from the Member Profile, we'll always use fresh data, which is better for the user experience when they update something on their LinkedIn and want to see that immediately reflected.

Type of Change 🐞

  • Feature - A non-breaking change which adds functionality.
  • Fix - A non-breaking change which fixes an issue.
  • Refactor - A change that neither fixes a bug nor adds a feature.
  • Documentation - A change only to in-code or markdown documentation.
  • Tests - A change that adds missing unit/integration tests.
  • Chore - A change that is likely none of the above.

Checklist ✅

  • I have done a self-review of my code.
  • I have manually tested my code (if applicable).
  • I have added/updated any relevant documentation (if applicable).

@ramiAbdou ramiAbdou self-assigned this Aug 22, 2025
@ramiAbdou ramiAbdou marked this pull request as ready for review August 22, 2025 16:27
@ramiAbdou ramiAbdou merged commit 9680dae into main Aug 22, 2025
3 checks passed
@ramiAbdou ramiAbdou deleted the rami/debug branch August 22, 2025 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant