parser data REFACTOR split NETCONF notification and reply parsing
Because there is never a situation when either of
these messages could be parsed directly, the transport
protocol metadata must first be handled. Also, the
old API did not allow for direct notification
parsing, always only both a reply and notification.
diff --git a/tools/lint/cmd_data.c b/tools/lint/cmd_data.c
index 2029ff1..919c45e 100644
--- a/tools/lint/cmd_data.c
+++ b/tools/lint/cmd_data.c
@@ -232,11 +232,11 @@
} else if (!strcasecmp(optarg, "edit")) {
options_parse |= LYD_PARSE_ONLY;
} else if (!strcasecmp(optarg, "rpc") || !strcasecmp(optarg, "action")) {
- data_type = LYD_TYPE_YANG_RPC;
+ data_type = LYD_TYPE_RPC_YANG;
} else if (!strcasecmp(optarg, "reply") || !strcasecmp(optarg, "rpcreply")) {
- data_type = LYD_TYPE_YANG_REPLY;
+ data_type = LYD_TYPE_REPLY_YANG;
} else if (!strcasecmp(optarg, "notif") || !strcasecmp(optarg, "notification")) {
- data_type = LYD_TYPE_YANG_NOTIF;
+ data_type = LYD_TYPE_NOTIF_YANG;
} else if (!strcasecmp(optarg, "data")) {
/* default option */
} else {