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

refactor: introduce cache for members list fetched by ZE #2331

Conversation

ap891843
Copy link
Contributor

@ap891843 ap891843 commented Jun 7, 2024

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • No regressions introduced

Checklist:

  • Each of my commits contains one meaningful change
  • I have performed rebase of my branch on top of the development
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have checked my code and corrected any misspellings

@ap891843 ap891843 force-pushed the feature/introduce_cache_for_member branch from 485ec93 to 5923a17 Compare June 7, 2024 12:12
@@ -132,7 +132,8 @@ describe("Tests Copybook download from DNS", () => {
"document-uri",
"DNS.PATH",
);
expect(allMemberMock).toHaveBeenCalledWith("DNS.PATH");
// cache resolves the members
expect(allMemberMock).not.toHaveBeenCalled();
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd suggest to make a new test (for datasets and uss), one verifies that the api is called, the other verifies usage of the cache.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

@ap891843 ap891843 force-pushed the feature/introduce_cache_for_member branch from 5923a17 to ce52efe Compare June 10, 2024 10:46
Signed-off-by: Aman Prashant <aman.prashant@broadcom.com>
@ap891843 ap891843 force-pushed the feature/introduce_cache_for_member branch from ce52efe to 524d1fa Compare June 10, 2024 11:35
@ap891843 ap891843 merged commit 71272ae into eclipse-che4z:development Jun 11, 2024
16 checks passed
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.

3 participants