Skip to content
This repository has been archived by the owner on Feb 28, 2022. It is now read-only.

JSON pipeline should not display error in production #280

Closed
rofe opened this issue Apr 24, 2019 · 1 comment · Fixed by #289
Closed

JSON pipeline should not display error in production #280

rofe opened this issue Apr 24, 2019 · 1 comment · Fixed by #289
Assignees
Labels
enhancement New feature or request released

Comments

@rofe
Copy link
Contributor

rofe commented Apr 24, 2019

Like the HTML and XML pipeline, the JSON pipeline should only output an error message in a non-production environment.

@rofe rofe added the enhancement New feature or request label Apr 24, 2019
@rofe rofe self-assigned this Apr 24, 2019
rofe added a commit that referenced this issue Apr 25, 2019
emit json from content.json, expose extension points, don't bleed errors in production

fix #230, fix #269, fix #280
adobe-bot pushed a commit that referenced this issue Apr 25, 2019
# [1.9.0](v1.8.0...v1.9.0) (2019-04-25)

### Features

* **json:** keep response.body as object ([263b637](263b637))
* **json:** refactoring json pipeline ([d67cf53](d67cf53)), closes [#230](#230) [#269](#269) [#280](#280)
@adobe-bot
Copy link

🎉 This issue has been resolved in version 1.9.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants