Nikola Marčetić
Nikola Marčetić
What about this ? Its not merged yet... and I am confirming this as a fix. I have a same problem and I just tested this for dynamic child elements,...
Needs more research and brainstorming, moving for `0.9`
Check out Kubernetes methodology [overview](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md#overview) Also [Ginkgo](http://onsi.github.io/ginkgo/) Looks great.
@mainflux/maintainers I took this issue to do research.
Great @nwneisen :) Take your time for research, then we can sync here and agree about implementation.
I fully agree with @chombium. We are missing requirements and concepts. I'm least concerned about the tech/tooling part. We agreed to continue the discussion here. I like your points @chombium...
@anovakovic01 Fully agree, let's remove everything we don't need in channels regarding access control (e.g connections) and keep just things that we need for messaging like topics, metadata, etc...
@chombium Good question ^ `What are we going to do about managing the thing and the CRUD operations on them` I would leave as is, so the ONLY user can...
We spoke about this few times before, missing `ID` on user structure as we have with any other entity in the system. So YES huge :+1: from my side @saeidakbari
@anovakovic01 I agree, it can stay like this, but is it not better at least for sake of consistency to add `ID` as we did it for any other entity?