Feature request: Improve error handling about restconf HOT 7 CLOSED

from restconf.

I will keep posting observations while I build a restconf interface.

For starters, something that was not immediate to me is that ApplyStartupConfig seems to not create [] or maps in the managed object. If a configuration is present for the map/[], I would let ApplyStartupConfig do the creation.

If the map/vector is not created, restconf only reports that there was a nil assignment to map/vector. It would probably simplify the debug process if we always printed the field under examination.

from restconf.

I was playing with your map example (https://freeconf.org/docs/examples/node-list-map/) and if in your go struct you forget one of the fields, restconf tells you that a field is missing but it doesn't tell you where or which one. Now that I played a bit with it I will start reading the documentation seriously. I bet that will clarify many things.

from restconf.

from restconf.

Thank you for the update!

from restconf.

I just pushed an update but instead of changing nodeutil.Reflect I created nodeutil.Node which you should check out. Easier and more powerful to use. It does have better error handling and should give field names.
Docs: https://freeconf.org/docs/examples/node-reflect/
You can reopen this if you still have issues

from restconf.

Thank you! Just in time, I got sidetracked again but I will work again on this project this week!

from restconf.