Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default display name format changed from version 4.x.x to 5.x.x #174

Open
asenfter opened this issue Nov 26, 2024 · 1 comment
Open

Default display name format changed from version 4.x.x to 5.x.x #174

asenfter opened this issue Nov 26, 2024 · 1 comment

Comments

@asenfter
Copy link

Hello everyone,

we encountered an issue when migrating from 4.2.0 to 5.x.x due to changes in the display name format. The new plugin configuration introduces the "Enable New Data Format" setting, which can be switched on or off.

Behavior:

  1. Enable New Data Format = unchecked:

    • Display name changes from <AF-Attribute-Name> to <AF-Element><pipe><AF-Attribute-Name>.
    • Example:
      • In version 4.2.0: pressure
      • In version 5.x.x: pump|pressure
  2. Enable New Data Format = checked:

    • Display name changes from <AF-Attribute-Name> to <AF-Attribute-Name> {element=<AF-Element> name=<AF-Attribute-Name> type=...}.
    • Example:
      • In version 4.2.0: pressure
      • In version 5.x.x: pressure {element=pump name=pressure type=...}

Issues:
The following problems occurred when testing both options:

  • Field overrides by name in panel configuration no longer work as expected.
  • Referencing fields in standard panel transformations fails.
  • Series names changed in histograms, legends, ...
  • ...

Expected Behavior:
We expected Enable New Data Format=unchecked to keep the exact display name format from version 4.2.0 for backward compatibility.

Was it intentional that the unchecked option differs from the old format? If not, can this be fixed in a future patch?

@asenfter
Copy link
Author

asenfter commented Dec 9, 2024

Dear @coderReview I'd be really grateful if you could take a look. Thank you so much in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant