sekur
commented
5 years ago Hi @quantang
I don't see any issues with your code so I'll try to replicate that pattern.
But I do have some suggestions on how you can condense the logic.
For one, the latest yang-js does not require a function for binding.
You can simply do something like:
const model = Yang.import(schema).bind({
'feature(AMF)': true,
'feature(VLAN)': true
}).eval({
'ietf-network:network': {}
});It's possible the .access is resolving something unintended? But you don't need to access a specific module in order to set the data. As long as the datapath is in one of the "schema" import dependency chain, it should do what you expect.
BTW, latest yang-js also creates a parent Store instance attached to the model so you can also check the model.store to see if it got applied there.
Another possibility is that ietf-network module actually isn't one of the import dependencies of the at-network-topology-v1.yang?
Before, we used to allow .access() to get to the "store" which was attached to the Model class constructor. But this is no longer the case. Each Yang.import or such are disconnected from each other and there is no longer a Singleton Store where all models live.
Take a look at Store.coffee for how to work with multiple peer modules.
quantang
Hello @saintkepha,
I just got back on YANG schema related work and want to update my yang-js library to the latest version. However, I am not sure whether I am using it in the wrong way, as my code cannot work with the latest version.
Could you help me take a look where would be the problem?
Here is what my code looks like before:
My expectation is it will initialize my model with the 'ietf-network:networks' attribute, which is the root of my data. However, when I try to call the get() function, it always returns empty.
Here is my sample data structure:
Any idea? Cheers.