Skip to content

Refactor readme rendering logic #3760

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

Merged
merged 4 commits into from
May 2, 2018
Merged

Conversation

theacodes
Copy link
Contributor

Towards #3739
Original context: #3745

@theacodes
Copy link
Contributor Author

Gentle ping on this.

@brainwane
Copy link
Contributor

@aalmazan can you review this, if you have time?

@di
Copy link
Member

di commented May 2, 2018

I am (very slowly) reviewing & testing this.

Copy link
Member

@di di left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM aside from a very small nitpick

@@ -180,6 +180,7 @@ def test_detail_renders(self, db_request):
"project": project,
"release": releases[1],
"files": [files[1]],
"description": None,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a description to the ReleaseFactory.create call above, monkeypatch readme.render, assert that it's called w/ Release.description, and assert that this value is the stub from that call?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. :)

@theacodes
Copy link
Contributor Author

@di this should be ready to go now.

@di di merged commit a22d9f0 into pypi:master May 2, 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.

3 participants