fixing multiple metrics

[ppisljar]

Summary

resolves #62771

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[flash1293]

Tested and visualizations with more complex metrics and axes configurations render fine again.

Could you elaborate on how this fix works? It seems like this broke because something generic (in how state management works, it seems) got changed, but the fix only addresses a single local instance.

Is it because this is happening in a special tab?

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 377627e

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[ppisljar]

vis.setState was updated to allow changing type (where before if you changed type it would actually just change the .type property it would now really recreate that type (get the type def from registry, init default parameters etc). so when changing type default parameters got applied as nothing else got passed in. We are now passing whole state in and just updating the type.

[flash1293]

Thanks for the explanation @ppisljar tested and works as expected. A quick code search didn't show any other places where setState was called the wrong way.