Josh Romero

We'll update this issue to make sure the community is clear on the change: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/2088 But otherwise, @sipopo we agree with these changes and will plan to merge once the...

Yeah, "didn't test completely" just means "this _might_ work, but no guarantees". Maybe `You're using an untested version of Node.js. OpenSearch Dashboards has been tested to work with Node.js ${requiredVersion}....

I strongly favor Option 3 here, particularly because this is the solution already implemented by the `visualizations` app for this exact use case: to include the saved objects of other...

This will be on hold for now, with #2011 in its place.

@kavilla Sure, we could - to be honest, I'm not entirely clear on our overall approach to patch version backports. Do we greedily do it for any bugfix that's safe...

@Jon-AtAWS To help us prioritize various new visualization types, can you provide a little more context of your Sankey use-case? The type of data you're looking to compare, and the...

Sure - but precommit hooks can be annoying to override, in the case where the lockfile does need an update.

Now that we have some test coverage for saving and loading (thanks!), we should also include unit tests for this flow, particularly because there are five separate user flows that...

@pjfitzgibbons Just following up to see if you're able to update the PR an resolve conflicts or remove the `yarn.lock` file.

@jimkaba You bring up some good points, and most of them would apply to any visualization type that includes a timeseries axis or timestamp data. @btzeng This is something we...