LRS-35 The LRS should not require implementers to use the /xapi path prefix, as this is not part of the spec.
This PR allows the prefix to be customized (as a path from root with no trailing slash), and sets the default to /xapi so as not to break existing stuff.
The memory implementation is updated to account for the change in the processing of the more link
Note: since we don't want to be restrictive about config/environment it is up to the implementer to supply this option when constructing the LRS in:
The call to com.yetanalytics.lrs.pedestal.routes/build as the :path-prefix key
The call to com.yetanalytics.lrs.pedestal.interceptor/xapi-default-interceptors, via the com.yetanalytics.lrs.pedestal.interceptor/path-prefix pedestal service map key
I think we should eventually default it to the empty string when dependent projects are migrated to set it explicitly.
LRS-35 The LRS should not require implementers to use the
/xapi
path prefix, as this is not part of the spec.This PR allows the prefix to be customized (as a path from root with no trailing slash), and sets the default to
/xapi
so as not to break existing stuff.The memory implementation is updated to account for the change in the processing of the
more
linkNote: since we don't want to be restrictive about config/environment it is up to the implementer to supply this option when constructing the LRS in:
com.yetanalytics.lrs.pedestal.routes/build
as the:path-prefix
keycom.yetanalytics.lrs.pedestal.interceptor/xapi-default-interceptors
, via thecom.yetanalytics.lrs.pedestal.interceptor/path-prefix
pedestal service map keyI think we should eventually default it to the empty string when dependent projects are migrated to set it explicitly.