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

editing an existing visualisation and saving will not ask for confirmation and creates duplicate #7081

Closed
derkcrezee opened this issue Apr 28, 2016 · 5 comments

Comments

@derkcrezee
Copy link

When opening particular saved visualisations, when saving and overriding the visualisation, the UI will not ask me for a confirmation. Additionally, instead of overriding the saved visualisation, I now have two visualisations with the same name.

@rashidkpc
Copy link
Contributor

It sounds like someone went hacking around in the object editor and changed the name of something.

@derkcrezee
Copy link
Author

That could very well be the case, as I see that title in the URL and the title in the UI of the object settings is different. Is there any proper way to change the title of an visualisation, without having to recreate it and loosing all the references in the dashboards?

@pemontto
Copy link

pemontto commented May 10, 2016

I've seen this myself, is it sensible to allow a user to rename an object without updating the _id of the visualization as well?

This can be reproduced by creating a visualisation "Top-Devices", putting it on a dashboard then editing the title in the object editor "Top Devices - Modified Title". Now when you click the edit button and save the visualisation again there's no overwrite prompt because there's nothing stored under that _id "Top-Devices-Modified-Title":
id-title

Admittedly the object editor does say the feature is for advanced users, but it would be nice to have an option for it to update the _id when changing the title and avoid confusing situations like this:
visualisations

@rashidkpc
Copy link
Contributor

Replacing with #2735

@suraj-kamath
Copy link

Do we have a known-workaround for this issue ?

breehall added a commit that referenced this issue Aug 23, 2023
`87.1.0` ➡️ `87.2.0`

## [`87.2.0`](https://github.com/elastic/eui/tree/v87.2.0)

- `EuiResizableButton` is now available as a generic top-level export
([#7087](elastic/eui#7087))
- Added new `alignIndicator` prop to `EuiResizableButton`. Defaults to
`center`, and can now additionally be configured to `start` and `end`
([#7087](elastic/eui#7087))
- Updated `useGeneratedHtmlId` hook to use `React.useId` as the source
of unique identifiers when available
([#7095](elastic/eui#7095))

**CSS-in-JS conversions**

- Converted `EuiResizableButton` to Emotion; Removed
`$euiResizableButtonTransitionSpeed` and `$euiResizableButtonSize`
([#7081](elastic/eui#7081))
- Converted `EuiResizableCollapseButton` to Emotion
([#7091](elastic/eui#7091))

---------

Co-authored-by: Cee Chen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants