Skip to content

Two base classes have an unnamed group that clashes in intent with a subclass field (and vice versa) #1612

@PeterC-DLS

Description

@PeterC-DLS

Here's two instances that occurred in new base classes (@lukaspie and @mkuehbach):

  1. NXcomponent contains NXfabrication which clashes with fabrication in subclass NXfresnel_zone_plate
  2. NXapm_ranging (and also its NXprocess subgroups) and NXapm_reconstruction contain unnamed NXprogram groups but NXprocess has a program

Strictly, this is not a name collision though it can cause issues with autogenerated code and validators so it seems that perhaps

  1. NXfresnel_zone_plate could name its fabrication field to something more descriptive
  2. NXprocess could contain an NXprogram group or, conversely, NXapm_ranging and NXapm_reconstruction could specify named NXprogram groups

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions