Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Feature/add operation id to documentation #38

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Feature/add operation id to documentation #38

wants to merge 4 commits into from

Conversation

garygitton
Copy link

I added this field to be able to personalized methods of the sdks generated with swagger-codegen and zf-apigility-documentation-swagger.

Note: this depends on zfcampus/zf-apigility-documentation#70

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools-documentation-swagger; a new issue has been opened at laminas-api-tools/api-tools-documentation-swagger#4.

@weierophinney
Copy link
Member

This repository has been moved to laminas-api-tools/api-tools-documentation-swagger. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

  • Squash all commits in your branch (git rebase -i origin/{branch})
  • Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
  • Run the laminas/laminas-migration tool on the code.
  • Clone laminas-api-tools/api-tools-documentation-swagger to another directory.
  • Copy the files from the second bullet point to the clone of laminas-api-tools/api-tools-documentation-swagger.
  • In your clone of laminas-api-tools/api-tools-documentation-swagger, commit the files, push to your fork, and open the new PR.
    We will be providing tooling via laminas/laminas-migration soon to help automate the process.

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

Successfully merging this pull request may close these issues.

2 participants