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

Features/resources api responses #76

Merged
merged 11 commits into from
Jan 15, 2024
Merged

Conversation

curtwl
Copy link
Collaborator

@curtwl curtwl commented Dec 23, 2023

Description

Add @ApiResponse tags to team resources controller

Issue link

Fixes #66

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Tested with Swagger.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Copy link
Collaborator

@cherylli cherylli left a comment

Choose a reason for hiding this comment

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

looks good, just a few minor things,

was the latest dev pulled into this branch?

should we put "examples" on the DTOs too?
image

There's an undocumented change here (the POST endpoint)
image

@cherylli
Copy link
Collaborator

Not sure if you noticed the 400 bad request response in the POST endpoint, the message part is an array, which is different from other responses. I think it might be because there are multiple validators.

Should we add another BadRequestErrorResponse (but with another name) for this?

@curtwl
Copy link
Collaborator Author

curtwl commented Dec 27, 2023

Not sure if you noticed the 400 bad request response in the POST endpoint, the message part is an array, which is different from other responses. I think it might be because there are multiple validators.

Should we add another BadRequestErrorResponse (but with another name) for this?

I see what you mean. Does this look good?

image
image

@cherylli
Copy link
Collaborator

Not sure if you noticed the 400 bad request response in the POST endpoint, the message part is an array, which is different from other responses. I think it might be because there are multiple validators.
Should we add another BadRequestErrorResponse (but with another name) for this?

I see what you mean. Does this look good?

image image

yeah that looks good. thank you!

cherylli
cherylli previously approved these changes Dec 30, 2023
Copy link
Contributor

@smurph7894 smurph7894 left a comment

Choose a reason for hiding this comment

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

I think this also may need to pull some commits from the dev branch.

src/resources/resources.response.ts Outdated Show resolved Hide resolved
smurph7894
smurph7894 previously approved these changes Jan 11, 2024
Copy link
Contributor

@jenny-alexander jenny-alexander left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@curtwl curtwl merged commit d7c0e73 into dev Jan 15, 2024
1 check passed
@curtwl curtwl deleted the features/resources-api-responses branch January 15, 2024 01:36
@jenny-alexander
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add @ApiResponse tags in controller classes already implemented (resources)
4 participants