[YANGTOOLS-72] Generated code conflict not reported by yangtools Created: 14/Jan/14 Updated: 10/Apr/22 Resolved: 04/Mar/14 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Maros Marsalek | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
When using sal code generator with yang maven plugin on a yang file with typedef and grouping sharing the same name, no warning is produced and only the code for typedef is generated. example yang file content: typedef network-topology-ref { type instance-identifier; ... } grouping network-topology-ref { } The generated code for this yang contains only one class named NetworkTopologyRef for the typedef. A warning about this would be welcomed. |
| Comments |
| Comment by Robert Varga [ 23/Jan/14 ] |
|
This will be addressed after Hydrogen release. |
| Comment by Martin Vitez [ 04/Mar/14 ] |
|
Fixed: |
| Comment by Tony Tkacik [ 04/Mar/14 ] |
|
Generated Code conflict is reported. Opening new enhancement bug for actually not conflicting of valid yang definitions https://bugs.opendaylight.org/show_bug.cgi?id=476. The support for cooexistence of both, will need to be addressed by new binding specification. |