Skip to content

Hash portion of the class name not guaranteed to be consistent with same component #416

@hardysabs2

Description

@hardysabs2

I understand that the hash portion of the class name can be impacted my environmental changes like the version of vite or the version of the plugin and with no change to the component still cannot be cast iron guaranteed not to change.

While the human readable class name (portion) is helpful to analysis tools for users to setup analysis paths and activities, the class name must be guaranteed not to change (except at most due to the change in the styling itself) else all the analysis set up is broken (in our case using Pendo.io).

Can this be implemented?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions