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

feature: WEOS-1384 As a developer I should be able to specify a Go template I want to use to render a response #144

Merged
merged 5 commits into from
Mar 15, 2022

Conversation

shaniah868
Copy link
Contributor

  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • What is the current behavior? (You can also link to an open issue here)

-Go templates are being rendered in the default response middleware and returned
-Added a check for parameters and pull them out of the context so that the execute function can use the data directly

  • What is the new behavior (if this is a feature change)?

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

  • Other information:

…mplate I want to use to render a response

-Added fixtures for test
-Added tests for functionailty
# Conflicts:
#	controllers/rest/fixtures/blog.yaml
…mplate I want to use to render a response

-Added template extension
-Added functionality for rendering template in default response middleware
…mplate I want to use to render a response

-Updated the html files
-Added checks for parameter and pull them out of the context so that it can be used
-Updated test
@RandyDeo RandyDeo merged commit 2679704 into feature/WEOS-1384 Mar 15, 2022
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.

2 participants