how could i successfully parse configuration with "remove" attribute with lyd_parse_data_mem api?

[lyzliyuzhi91]

module a {
    yang-version 1.1;
    namespace "urn:huawei:xxx:unit-test:a";
    prefix a;

    container c1 {
        leaf num-leaf {
            type uint32;
        }
    }
}

    source = "{\"a:c1\":{\"num-leaf\":\"\",\"@num-leaf\":{\"ietf-netconf:operation\":\"remove\"}}}";
    uint32_t parse_opts = LYD_PARSE_STRICT | LYD_PARSE_ONLY | LYD_PARSE_NO_STATE;
    err = lyd_parse_data_mem(ctx, source, LYD_JSON, parse_opts, LYD_VALIDATE_PRESENT, &out);
    ASSERT_EQ(err, LY_SUCCESS);

But err return LY_EVALID .
Thanks.

[michalvasko]

Look at the error message, if you do not want to enable logging then with ly_last_errmsg(), for example. Only one problem I can think of based on this brief description, have you loaded the ietf-netconf YANG into the context?

[lyzliyuzhi91]

What i want to do is wanting to enforce some validation for the <config> node in <edit-config> , for example, the newly created/merged node's value, but I think the value of nodes to be deleted should not be validated?

[michalvasko]

Right, I have missed that the value you are using is invalid. If you want to parse it, you have to use LYD_PARSE_OPAQ but such nodes will not validate. That should not matter, though, so just get rid of LYD_VALIDATE_PRESENT, there is nothing to validate in an edit config data anyway.

[lyzliyuzhi91]

But once I use LYD_PARSE_OPAQ, I cannot parse the value of newly create/merge right?

there is nothing to validate in an edit config data anyway

Why? I want to check the validation for the configuration. For example, if a string-type leaf node a is restricted by length 8..20, and the user configure a with value "xxx". And once I get the edit-config rpc message, I just want to get a result that value of a is incorrect by libyang's validation function.

[michalvasko]

But once I use LYD_PARSE_OPAQ, I cannot parse the value of newly create/merge right?

Do not understand what you mean, what the flag does is parses invalid nodes as opaque nodes, valid nodes are parsed normally.

Why? I want to check the validation for the configuration.

You are not supposed to be validating the edit config (because it can be invalid as seen in this case) but rather the configuration after the edit is applied.