Open weierophinney opened 4 years ago
+1 doesn't work for me as well. For now, I am manipulating the config files directly.
Originally posted by @kevinpapst at https://github.com/zfcampus/zf-apigility-documentation/issues/18#issuecomment-66037329
What's the best workflow / method for testing this part of Apigility? I'm familiar with XDebug, but unsure where to start on checking if the failure lies in the reading in of my hacked/customized config... or elsewhere.
I had used the Admin tool + Documentation generator at first, but after doing a ton of work, the admin tool just seems stuck and can no longer read the module.config.php
(s) that I have hacked together.
One idea I have, is to grab a skeleton and re-do all of the documentation for each and every service..
Originally posted by @EMCP at https://github.com/zfcampus/zf-apigility-documentation/issues/18#issuecomment-67785093
Should be fixed last release
Originally posted by @snapshotpl at https://github.com/zfcampus/zf-apigility-documentation/issues/18#issuecomment-100337683
When updating the documentation for a REST service I'm able to edit and save the global description, but unable to edit and save any of the individual GET / Collection / Entity documentation entries. It states that it has saved but does not update
Originally posted by @cpats007 at https://github.com/zfcampus/zf-apigility-documentation/issues/18