Skip to content
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

0.5.1 Release #60

Merged
merged 5 commits into from
Apr 14, 2018
Merged

0.5.1 Release #60

merged 5 commits into from
Apr 14, 2018

Conversation

kirbs-
Copy link
Owner

@kirbs- kirbs- commented Apr 14, 2018

No description provided.

Wim van Mourik and others added 5 commits March 26, 2018 14:50
When executing 'behave' cell magic in a notebook, behave prints output
to standard out. (http://behave.readthedocs.io/en/latest/tutorial.html)

Example output:
"""
    Feature: showing off behave # features/tutorial.feature:1

      Scenario: run a simple test        # features/tutorial.feature:3
        Given we have behave installed   # features/steps/tutorial.py:3
        When we implement a test         # features/steps/tutorial.py:7
        Then behave will test it for us! # features/steps/tutorial.py:11

    1 feature passed, 0 failed, 0 skipped
    1 scenario passed, 0 failed, 0 skipped
    3 steps passed, 0 failed, 0 skipped, 0 undefined
"""

Issue:
    Even when no hide checkbox is selected, I don't see standard output back in the html file.

Fix:
    I have added a Jinja elif for json key output.text; it just shows everything inside the json value.

Perhaps the filter logic could be better, but I am not that familiar with notebook output options.
IE; are data and text mutually exclusive?
Or are there even more types, which might warrant an {%- else -%}{{super()}}?
@kirbs-
Copy link
Owner Author

kirbs- commented Apr 14, 2018

Resolves #54, #58, and #50.

@kirbs- kirbs- merged commit a5a76d4 into master Apr 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant