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

Refactor using merge #23

Merged
merged 10 commits into from
Jan 15, 2024
Merged

Refactor using merge #23

merged 10 commits into from
Jan 15, 2024

Conversation

caindy
Copy link
Contributor

@caindy caindy commented Jan 13, 2024

No description provided.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@getorymckeag Turns out the new toolchain support yaml merge <<: *ref, so I was able to DRY up GET/HEAD a bit while establishing a pattern to ensure GET responses are HEAD responses with content. It's a ton cleaner even though it's not a lot shorter.

@caindy caindy force-pushed the refactor-using-merge branch 4 times, most recently from dc3b5ef to 480ebdf Compare January 15, 2024 19:02
@caindy caindy marked this pull request as ready for review January 15, 2024 19:10
Copy link

github-actions bot commented Jan 15, 2024

Document: �[35m./docs/openapi.yaml�[39m stats:

�[31m🚗 References: 89
�[39m�[35m📦 External Documents: 0
�[39m�[37m📈 Schemas: 60
�[39m�[33m👉 Parameters: 9
�[39m�[36m🔗 Links: 0
�[39m�[32m➡️ Path Items: 28
�[39m�[33m👷 Operations: 57
�[39m�[37m🔖 Tags: 7
�[39m�[90m
./docs/openapi.yaml: stats processed in 51ms

�[39m

@caindy caindy merged commit 98a192c into 1.0.0-wip Jan 15, 2024
2 of 3 checks passed
@caindy caindy deleted the refactor-using-merge branch January 15, 2024 20:12
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.

1 participant