Skip to content

Conversation

g-jaskowski
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation
  • Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)
https://hyland.atlassian.net/browse/ACS-10165
It's possible to select libraries that user doesn't have access to in search Location filter. In such case no items appear in search results.

What is the new behaviour?
Selectable libraries will always provide search results (unless actually empty)

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

expect(component.context.filterLoaded.next).toHaveBeenCalled();
});

it('should populate LOCATION field options with sites and predefined values from config', (done) => {
Copy link
Contributor Author

@g-jaskowski g-jaskowski Oct 2, 2025

Choose a reason for hiding this comment

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

For some reason it treated an existing unit test that had one line changed as completely new code and newly added unit test as edited code

Copy link

sonarqubecloud bot commented Oct 2, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants