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

Required options for validators #70

Open
nuxwin opened this issue Jul 23, 2015 · 2 comments
Open

Required options for validators #70

nuxwin opened this issue Jul 23, 2015 · 2 comments
Assignees

Comments

@nuxwin
Copy link

nuxwin commented Jul 23, 2015

Usage of admin ui to add validators is not really obvious. For instance, when adding ZF\Apigility\Doctrine\Server\Validator\NoObjectExists validator, it should be clearly stated that the entity_class option is mandatory. It took me 10 minutes to figure out. At end, I've just looked at my js debugger but... From my point of view, there should have two parts: Required options and optional options OR at least, an error message which is clear enough. Saying something like currently " Api communication problem" is not really clear for end-users.

@weierophinney
Copy link
Member

Ping @ezimuel and/or @jguittard — could one of you look into this, please?

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools-admin-ui; a new issue has been opened at laminas-api-tools/api-tools-admin-ui#15.

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

No branches or pull requests

3 participants