-
Notifications
You must be signed in to change notification settings - Fork 18
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
Warning message is also added in that particular section along with text. #52
Comments
@madhuriupadhye thank you for creating the issue. Make sure you have the valid Restructured Text before running Betelgeuse. I think it is able to remove that warning, but having that makes us aware that our RST formatting is not good. I've been thinking on a way to fix it, but I have not decided what is best, skip the test case if the parse can't be successfully completed (which is bad because that is not a blocker for creating the test case), just remove the warning and have poorly formatted information on Polarion (by removing the warning you will end up with a list of 3 elements and one paragraph starting with the literal string |
Removing the bug label since this is not a Betelgeuse bug but a feature to notify when bad RST docstring is received. |
@madhuriupadhye can you paste the test docstring test case which created this error? |
The issue is mostly like because the second line of item 4 was not indented, it should be like this:
While it should be something like:
|
I can't reproduce this with the latest version of Betelgeuse. |
Suppose after running the .py file contains some warning like (WARNING/2) Enumerated list ends without a blank line; unexpected unindent for steps section then it was added in steps section of polarion with steps.
![screenshot from 2016-07-07 12 10 26](https://cloud.githubusercontent.com/assets/18697962/16644663/481f5ff8-443c-11e6-8b27-2d53c2c8bbeb.png)
The text was updated successfully, but these errors were encountered: