Github user baibaichen commented on the issue:
https://github.com/apache/eagle/pull/765
+1 on @haoch. By the way, from the perspective of priority, backend
validation would be solved at first.
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/765
But it should be better to add validate in both front-end and backend at
same time :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/765
I think the feature should be added into backend
`org.apache.eagle.service.metadata.resource.MetadataResource#validatePolicy()`
---
If your project is set up for it, you can reply to this email and hav
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/765
+1, LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
