fix: Added in-code default bot project file to use for old bots #8181
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
In a recent change #7870, all the existing bot templates that existed in
/extensions/samples/assets/projects
were removed. There was a piece of code inside ofBotProject.init()
that would use the.botproj
file of the first bot template in that directory as a skeleton to be filled out for old bots that needed to create a project file.Since there are no longer any bot templates in that directory, this piece of code always returns
undefined
and no.botproj
file is created for old bots. This was causing bots imported from PVA to throw an error when being opened because of a missing project fileThis PR takes the old
.botproj
skeleton that was present in the EchoBot sample and puts it into the code to be referenced by old bots.#minor