Option for custom context on serverless Express server #223
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.
When using the servless options, LTIJS defaults to the requester baseUrl and its "/" context when redirecting back to our application. This makes it impossible for this to work in situations where we want LTIjs to use a separate context from the one used by the main web application.
This PR makes it possible to specify a custom context that will be used by the Express server when dealing with LTIjs messaging.
Example usage:
This will result in "/ltitool/launch", "/ltitool/login", "/ltitool/register" to be used by the Express server as intended.