Add Option to Specify Decoupled Router API Prefix in JsonApiClient

Created on 7 February 2024, 10 months ago
Updated 15 April 2024, 7 months ago

Problem/Motivation

It is possible to provide an API base for decoupled router when using the decoupled-router-client directly. But the instance created by the json-api client currently only uses the default.

Steps to reproduce

Proposed resolution

Introduce something like a decoupledRouterApiBase (is there a better name?) option for the json-api-client.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States brianperry

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024