Why, when the NHG count is 0, does it need to be populated with a single next hop?”

[JackJia812]

33 is actually a group, but when it is passed to the dplane, it becomes a single next hop.

ID: 33 (zebra)
     RefCnt: 2
     Uptime: 00:01:48
     VRF: default(bad-value)
     Depends: (34) (35)
           is directly connected, vlan10 (vrf default) inactive, weight 1
           is directly connected, vlan20 (vrf default) inactive, weight 1
ID: 34 (zebra)
     RefCnt: 3
     Uptime: 00:01:57
     VRF: default(IPv6)
     Interface Index: 1377
           is directly connected, vlan10 (vrf default) inactive, weight 1
     Dependents: (33)
ID: 35 (zebra)
     RefCnt: 3
     Uptime: 00:01:57
     VRF: default(IPv6)
     Interface Index: 1378
           is directly connected, vlan20 (vrf default) inactive, weight 1
     Dependents: (33)

		if (dplane_ctx_get_nhe_nh_grp_count(ctx)) {
			const struct nexthop_group *nhg;
			const struct nhg_resilience *nhgr;

			nhg = dplane_ctx_get_nhe_ng(ctx);
			nhgr = &nhg->nhgr;
			if (!_netlink_nexthop_build_group(
				    &req->n, buflen, id,
				    dplane_ctx_get_nhe_nh_grp(ctx),
				    dplane_ctx_get_nhe_nh_grp_count(ctx),
				    !!nhgr->buckets, nhgr))
				return 0;
		} else {
			const struct nexthop *nh =
				dplane_ctx_get_nhe_ng(ctx)->nexthop;   <-----here, why?
			afi_t afi = dplane_ctx_get_nhe_afi(ctx);