fix: unify runtime path from ejecting #6520
Merged
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.
Description
issue
in 1.3.1 the eject runtime path is the relative path for the bot folder.
But in 1.4.0 the path is the relative path for the bot/settings.
So the bot created by 1.3.1 with custom runtime can't work.
fix
make the 1.3.1 and 1.4.0 use the same runtime path when do eject.
if the runtime is new runtime, still use the relative path for the bot/settings.
Task Item
#minor
closes #6519
Screenshots