fix: Forward path mapping rules to backend process #11
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.
What was the problem/requirement? (What/Why)
When running in daemon mode, the path mapping rules were not being forwarded from the frontend runner to the backend runner. Integration clients that rely on the adaptor's http_server for path mapping were failing, as the path mapping rules on the backend were empty.
What was the solution? (How)
Provide the path mapping data to the Frontend running during initialization so they can be passed to the backend process.
What is the impact of this change?
The backend process contains the path mapping rules and is able to provide them to the client.
How was this change tested?
Was this change documented?
Updated docstring.
Is this a breaking change?
No.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.