fix(addons): drop whole-cache flush on addon settings save - #25
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opis
Odpowiedź na uwagę w review #21: \AddonController::saveSettings()\ wywoływało \Cache::flush(), czyszcząc cały cache aplikacji przy każdym zapisie ustawień dodatku.
Zmiana
Uzasadnienie
Dodatki (CompanyLookup, KSeF, OpenBRIS, CEIDG) nie cache'ują ustawień ani odpowiedzi — odczytują bezpośrednio przez \AddonSetting::getForAddon()/getSetting()\ z DB. \cache_ttl\ z konfiguracji dodatku istnieje jako deklaratywny parametr, ale nigdzie nie jest używane. W tej sytuacji nie ma konkretnego klucza do celowego \Cache::forget(), a flush całego cache to czysta strata (kasuje niepowiązane cache na obciążonym panelu) bez żadnej korzyści — dlatego zamiast \ orget()\ usuwam wywołanie w całości.