Rather than doing tricky web application replacements at package activation time, it would be better if the static file handlers supported setting the base URL (for both Angular and React) at runtime based on %request.Application which will possibly include the CSPInstanceName.
e.g., if I have a web application /personal, and it's served via CSPInstanceName iris20241, %request.Application will have /iris20241/personal/. This should automatically be set as the base URL in staticFilesHandler.
Taking this approach will support cases where the same instance is accessed both with and without a CSPInstanceName and avoid needing a fraught and super-ugly publicURL expression, like:
<Resource Name="/react/copilot-mockup" ProcessorClass="pkg.isc.ipm.js.react.processor" publicURL="#{$Select($Data(^%SYS("WebServer","URLPrefix"),prefix)#2&&(prefix'=""):"/"_prefix,1:"")}/personal" />
An error in which ended up leading to #16 .
For the sake of performance we'll probably want to cache file contents with URL replacements performed.
Rather than doing tricky web application replacements at package activation time, it would be better if the static file handlers supported setting the base URL (for both Angular and React) at runtime based on %request.Application which will possibly include the CSPInstanceName.
e.g., if I have a web application /personal, and it's served via CSPInstanceName iris20241, %request.Application will have /iris20241/personal/. This should automatically be set as the base URL in staticFilesHandler.
Taking this approach will support cases where the same instance is accessed both with and without a CSPInstanceName and avoid needing a fraught and super-ugly publicURL expression, like:
An error in which ended up leading to #16 .
For the sake of performance we'll probably want to cache file contents with URL replacements performed.