This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
[Botskills] Show all language output when there's an issue with a LU file #3262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
auto-assign
bot
requested review from
darrenj,
lauren-mills,
lzc850612,
pavolum,
peterinnesmsft,
ryanisgrig,
sidmore and
taicchoumsft
lauren-mills
approved these changes
Apr 2, 2020
ryanisgrig
approved these changes
Apr 2, 2020
lzc850612
approved these changes
Apr 2, 2020
darrenj
approved these changes
Apr 6, 2020
delete-merged-branch
bot
deleted the
southworks/feature/southworks/botskills/fix-error-logging
branch
3 tasks
lauren-mills
added a commit
that referenced
this pull request
Jun 2, 2021
…/show-multiple-logs [PORT #3262][Botskills] Show all language output when there's an issue with a LU file
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Purpose
What is the context of this pull request? Why is it being done?
Fix the issue #3196
At the moment, when botskills processes multiple languages and an error occurs while parsing LU files it will stop processing any subsequent LU file, therefore no further error will be logged.
With these changes, when there is an issue while parsing multiple languages with Ludown it will show all the error messages if there are issues with more than one, instead of showing only the first error message.
Changes
Are there any changes that need to be called out as significant or particularly difficult to grasp? (Include illustrative screenshots for context if applicable.)
The exception throwing in
executeLudownParseandexecuteDispatchAddis changed to error loging.After processing each language, if there was an error it will throw an exception.
Tests
Is this covered by existing tests or new ones? If no, why not?
-
Feature Plan
Are there any remaining steps or dependencies before this issue can be fully resolved? If so, describe and link to any relevant pull requests or issues.
Checklist
General