-
Notifications
You must be signed in to change notification settings - Fork 33
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
Development #1975
Development #1975
Conversation
The useSettings hook repeated calls to settings API after a recent version, probably after AI Content creator as that hooks to function to each block. After trying various methods, I settled on this one as it seems to work with all the current usage of useSettings that we have in Otter. I also tried to use a better implementation but those seem to not always work with the various use cases that we have with Otter. (as in using the Data Store for saving/retrieving the data) In the future, I'd avoid using useSettings in plugins as now Gutenebrg has built-in methods to use Settings API from the store, and as we work on different parts of Otter, we can try to remove the existing usage of useSettings.
fix: otter making repeated api calls
Bundle Size Diff
|
Plugin build for 25efcd0 is ready 🛎️!
|
E2E TestsPlaywright Test Status: Performance ResultsserverResponse: 204.45, firstPaint: 597.55, domContentLoaded: 1727.35, loaded: 1729.5, firstContentfulPaint: 10946, firstBlock: 18279.5, type: 43.6, minType: 40.99, maxType: 46.62, typeContainer: 13.89, minTypeContainer: 12.01, maxTypeContainer: 16.82, focus: 65.43, minFocus: 58.17, maxFocus: 74.59, inserterOpen: 27.79, minInserterOpen: 23.73, maxInserterOpen: 33.06, inserterSearch: 8.79, minInserterSearch: 8.04, maxInserterSearch: 10.49, inserterHover: 41.13, minInserterHover: 36.92, maxInserterHover: 45.4, listViewOpen: 159.99, minListViewOpen: 137.95, maxListViewOpen: 174.77 |
@HardeepAsrani Tested and the Patterns and OpenAI API work fine 👍 |
@irinelenache Thank you, I've updated it. Can you try again? Thank you! Make sure to also test non-Stripe part again to confirm the changes didn't cause anything already tested from working. I tested on my side but having a second pair of eyes helps. |
@HardeepAsrani Tested and everything's fine now 🚀 |
🎉 This PR is included in version 2.5.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Closes #1973