You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a fresh clean pull of Apigility, when editing documentation for a service, the only field that is stored in the documentation.config.php file is the service description. All the fields for the collection, entity and their respective verbs are discarded. Of note: I pulled down version 1.0.3 of Apigility and the documentation works as expected.
Attached are screen shots of the form before and after save.
@spectravp When you say "fresh clean pull" what exactly to you mean? I experienced the same as you from a download of the v1.0.4 from the Apigilty website. Do you mean that, or from current master? I ask because of this closed issue #232 The documentation for a Code-Connected service doesn't get saved. I will be trying HEAD this week.
On a fresh clean pull of Apigility, when editing documentation for a service, the only field that is stored in the documentation.config.php file is the service description. All the fields for the collection, entity and their respective verbs are discarded. Of note: I pulled down version 1.0.3 of Apigility and the documentation works as expected.
Attached are screen shots of the form before and after save.
Originally posted by @spectravp at zfcampus/zf-apigility-admin#241
The text was updated successfully, but these errors were encountered: