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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(offline): return correct value from clearSensitiveCaches #1008

Merged

Conversation

KaiVandivier
Copy link
Contributor

Previously, when clearSensitiveCaches didn't resolve to a relevant value, caches.delete(key).then(() => undefined) was returned in Promise.all to satisfy typescript, but I forgot to remove the undefined resolution when I copied in a refactor from the app platform that made clearSensitiveCaches resolve to a boolean indicating if any caches were deleted. Fixed that and some tests so that it resolves to the right boolean 馃憤

@KaiVandivier KaiVandivier requested a review from a team September 15, 2021 14:58
Copy link
Contributor

@Mohammer5 Mohammer5 left a comment

Choose a reason for hiding this comment

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

LGTM

@KaiVandivier KaiVandivier merged commit 02c2c6c into 2.x Sep 16, 2021
@KaiVandivier KaiVandivier deleted the fix-return-correct-response-from-clearSensitiveCaches branch September 16, 2021 08:19
dhis2-bot added a commit that referenced this pull request Sep 16, 2021
## [2.12.1](v2.12.0...v2.12.1) (2021-09-16)

### Bug Fixes

* **offline:** return correct value from clearSensitiveCaches ([#1008](#1008)) ([02c2c6c](02c2c6c))
@dhis2-bot
Copy link
Contributor

dhis2-bot added a commit that referenced this pull request Sep 17, 2021
# [3.2.0](v3.1.0...v3.2.0) (2021-09-17)

### Bug Fixes

* **offline:** return correct value from clearSensitiveCaches ([#1008](#1008)) ([4b68b22](4b68b22))

### Features

* **offline:** add 'clear sensitive caches' function ([01749aa](01749aa))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

4 participants