feat: predefined endpoints for CMS REST product list component #1495
Conversation
This file contains 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
…preperation) (#1463) * refactor ProductsService, SuggestService and FilterService to an abstract class and an ICM specific implementation * prerequisite for using alternative Sparque services
…ice, documentation) (#1463) * basic integration but no replaced services and REST requests (comes with additional commit)
DiverDori
force-pushed
the
feature/predefined_endpoints_for_rest_component
branch
from
a48523b to
f6df09c
Compare
DiverDori
force-pushed
the
feature/predefined_endpoints_for_rest_component
branch
from
f6df09c to
9c77940
Compare
shauke
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Type
[ ] Bugfix
[ x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[ ] Other:
What Is the Current Behavior?
The REST Component can call any REST endpoint and has to be configured all seperately. If there several components, that call a certain sparque workspace, this has to be configered in each instance.
Issue Number: Closes #
What Is the New Behavior?
The sparque endpoint configuration of the PWA can be used to configure the REST component in ICM by using the "sparque://" notation, the same goes for "icm://" to use icm_base_url.
Does this PR Introduce a Breaking Change?
[ ] Yes
[x ] No
Other Information
AB#89012