Add endpoint to export retrospective as JSON or Markdown#29
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces an export feature for retrospectives, allowing users to export retrospective data as either JSON or Markdown. The main changes include a new API endpoint, request/response types, validation, and the Markdown conversion logic. Below are the most important changes grouped by theme:
API Enhancements:
/retrospective/exportto export retrospectives in either JSON or Markdown format, including request validation and appropriate error handling. [1] [2]RetrospectiveExportRequesttype andExportTypeenum to specify export parameters and supported formats. [1] [2]Business Logic:
ConvertRetrospectiveToMarkdownmethod in theservicepackage to generate a Markdown-formatted export of a retrospective.Validation:
RetrospectiveExportRequest, ensuring valid retrospective IDs and export types.Dependency Injection:
ScheduleParamsstruct to include aLoggerdependency, ensuring logging is available throughout the schedule lifecycle.