Workflow: let each user doc one path per file, hiding a Swagger weakness.
S
Saul Ben Margolis
started a topic
over 3 years ago
If multiple developers or writers are working on a project, each should be able to document a specific set of paths (/mypath and /yourpath); but the Swagger 2.0 spec does not provide for this, perhaps because of issues with the JSON schema spec.
Whatever the internal block, a higher-level description language would add value by allowing for the workflow, especially for a complex API with a large number of paths.
In short, the user should be able to use a separate file to document a path.
1 person likes this idea
1 Comment
Ted Epstein
said
over 2 years ago
Saul,
Thanks for the suggestion. I'm happy to say that this is now fully resolved, with RepreZen API Studio's advanced multi-file support.
Saul Ben Margolis
If multiple developers or writers are working on a project, each should be able to document a specific set of paths (/mypath and /yourpath); but the Swagger 2.0 spec does not provide for this, perhaps because of issues with the JSON schema spec.
Whatever the internal block, a higher-level description language would add value by allowing for the workflow, especially for a complex API with a large number of paths.
In short, the user should be able to use a separate file to document a path.
1 person likes this idea