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.

Sign up for GitHub

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

Jump to bottom

In Render tolerate not being passed a context (#16842) #16858

Merged
merged 1 commit into from
Aug 29, 2021
Merged

In Render tolerate not being passed a context (#16842) #16858

merged 1 commit into from
Aug 29, 2021

Commits on Aug 29, 2021

  1. In Render tolerate not being passed a context (go-gitea#16842) 

    * In Render tolerate not being passed a context

It is possible for RenderString to be passed to an external renderer if markdown
is set to be rendered by an external renderer. No context is currently sent to these
meaning that this will error out.

Fix go-gitea#16835

Signed-off-by: Andrew Thornton <[email protected]>

* Add Context to Repo calls for RenderString

All calls from routers can easily add the context - so add it.

Signed-off-by: Andrew Thornton <[email protected]>
    @zeripath @6543
    zeripath authored and 6543 committed Aug 29, 2021
    Configuration menu
    Copy the full SHA
    7b5f989 View commit details
    Browse the repository at this point in the history