-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The errors of refactoring should be indicated #122
Comments
Fix should be available in nightly >= 15-2-18 |
Blocked 'cause of getgauge/gauge#943 |
Question
|
Showing multiple errors in the error popup may not be possible. VSCode's error pop up doesn't render properly for large/multiline texts. Right now, the errors are show with a tab spacing between them. If needed, we can add a button to open the output console where more information about the errors are indicated. |
Please verify the issue and update.
This issue has been closed. |
Actual behavior
No result
is displayed on the step textSteps to replicate
gauge-js
projectVowels in English language are "aeiou"
to an empty step. This should display the reason why refactoring failed clearly.Currently the output pane shows the error
{
is used in the stepHowever the IDE gives
No result
on the step.Version
Bug on story #81
The text was updated successfully, but these errors were encountered: