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

feat: expiresAt should only update on sync in js package #2253

Merged

Conversation

ShubhamPalriwala
Copy link
Contributor

What does this PR do?

the expiresAt now only gets updated when the sync happens with the Formbricks backend else it does not! Allowing for a much more updated client side data from the api

How should this be tested?

  • Test A
  • Test B

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read How we Code at Formbricks
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand bits
  • Ran pnpm build
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Formbricks Docs if changes were necessary

Copy link

vercel bot commented Mar 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
formbricks-cloud ⬜️ Ignored (Inspect) Visit Preview Mar 18, 2024 0:01am
formbricks-com ⬜️ Ignored (Inspect) Visit Preview Mar 18, 2024 0:01am

Copy link
Contributor

github-actions bot commented Mar 15, 2024

Thank you for following the naming conventions for pull request titles! 🙏

Copy link
Contributor

packages/js/src/lib/initialize.ts

There are several instances where the same configuration object is being fetched multiple times within the same function. This can be improved by fetching the configuration once and reusing it.
Create Issue
See the diff
Checkout the fix

    const currentConfig = config.get();
    config.update({
      environmentId: currentConfig.environmentId,
      apiHost: currentConfig.apiHost,
      userId: currentConfig.userId,
      state: {
        ...currentConfig.state,
        attributes: { ...currentConfig.state.attributes, ...c.attributes },
      },
      expiresAt: currentConfig.expiresAt,
    });
git fetch origin && git checkout -b ReviewBot/Impro-b43fvp3 origin/ReviewBot/Impro-b43fvp3

packages/js/src/lib/person.ts

Similar to the previous suggestion, the configuration object is being fetched multiple times within the same function. This can be improved by fetching the configuration once and reusing it.
Create Issue
See the diff
Checkout the fix

    const currentConfig = config.get();
    config.update({
      environmentId: currentConfig.environmentId,
      apiHost: currentConfig.apiHost,
      userId: currentConfig.userId,
      state: {
        ...currentConfig.state,
        attributes: {
          ...currentConfig.state.attributes,
          [key]: value.toString(),
        },
      },
      expiresAt: currentConfig.expiresAt,
    });
git fetch origin && git checkout -b ReviewBot/Impro-7x9k9uo origin/ReviewBot/Impro-7x9k9uo

@mattinannt mattinannt changed the title feat: (js package) expiresAt should only update on sync feat: expiresAt should only update on sync in js package Mar 15, 2024
Copy link
Member

@mattinannt mattinannt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ShubhamPalriwala thank you for this; looks great! :-)

@mattinannt mattinannt added this pull request to the merge queue Mar 18, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 18, 2024
@mattinannt mattinannt added this pull request to the merge queue Mar 18, 2024
Merged via the queue into main with commit 5c9e59b Mar 18, 2024
14 checks passed
@mattinannt mattinannt deleted the shubham/for-1983-js-expiresat-should-only-update-on-sync branch March 18, 2024 12:22
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.

None yet

2 participants