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

[ACS-9166] Migrate Saved Searches to preferences API from config file #10559

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

MichalKinas
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)

What is the new behaviour?

Saved Searches will no longer be stored in configuration file in favor of using preferences API. Existing data will be automatically migrated and configuration file will be automatically deleted.
https://hyland.atlassian.net/browse/ACS-9166

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:

@@ -84,4 +84,25 @@ export class PreferencesApi extends BaseApi {
queryParams
});
}

updatePreference(personId: string, preferenceName: string, preferenceValue: string): Promise<PreferenceEntry> {
Copy link
Contributor

Choose a reason for hiding this comment

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

should we have some unit tests for this? I see for other APIs we have unit tests like for tag api file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I wonder if we actually need them, to be honest they're quite outdated, a lot of APIs are not covered and maybe for the future we could think of a better solution for this but for now I would not add new unit tests there

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.

3 participants