# What happened to editableVis() **URL:** \ **Category:** Kibana\ **Created:** [January 29, 2019, 4:24pm UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208 "2019-01-29T16:24:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Dan\_Crooks](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_crooks/32/42266_2.png) [@Dan\_Crooks](https://discuss.elastic.co/u/Dan_Crooks)\ **Post date:** [January 29, 2019, 4:24pm UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208/1 "2019-01-29T16:24:13Z")
We are in the process of upgrading from Kibana 5.6 to 6.5.4. In 5.6, we had access to a function, `vis.getEditableVis()`. In custom visualizations, this would give give access to the part of the scope that was being watched by the 'Apply changes' button. That function is not available in 6.5.4. It seems like what is used now is `$scope.editorState`, however I do not have that in my scope in a custom visualization. Where does the `editorState` get created and how do I make it available in my custom vis? ---
**Author:** ![Dan\_Crooks](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_crooks/32/42266_2.png) [@Dan\_Crooks](https://discuss.elastic.co/u/Dan_Crooks)\ **Post date:** [January 29, 2019, 9:44pm UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208/2 "2019-01-29T21:44:46Z")
Found something in the [blog](https://www.elastic.co/blog/upcoming-kibana-plugin-api-changes-in-6-4) for 6.4 that says `vis.params` should be moved to `editorState.params`, but it doesn't give much more information. ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [January 29, 2019, 10:48pm UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208/3 "2019-01-29T22:48:19Z")
This was removed with a refactoring which was done for 6.0: [https://github.com/elastic/kibana/pull/11786](https://github.com/elastic/kibana/pull/11786), in an effort to move away from visualizations being explicitly written in AngularJS. [https://www.elastic.co/blog/developing-new-kibana-visualizations](https://www.elastic.co/blog/developing-new-kibana-visualizations) should provide an explanation of the refactoring which took place during 6.0, and the public APIs are now documented here: [https://www.elastic.co/guide/en/kibana/6.5/development-create-visualization.html](https://www.elastic.co/guide/en/kibana/6.5/development-create-visualization.html) ---
**Author:** ![ppisljar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppisljar/32/11588_2.png) [@ppisljar](https://discuss.elastic.co/u/ppisljar)\ **Post date:** [January 30, 2019, 8:11am UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208/4 "2019-01-30T08:11:28Z")
Hey, In 6.x we have Angular visualization type, but also Base (pure js) and React. The angular visualization type is deprecated, and will be removed with 7.0, so it might make more sense (if possible) to migrate your custom visualization directly to either Base or React visualization type. Do you think that would be possible ? We have some documentation around developing new visualizations: [https://www.elastic.co/guide/en/kibana/6.5/development-create-visualization.html](https://www.elastic.co/guide/en/kibana/6.5/development-create-visualization.html) and there is this blog post: > **[Creating new Kibana visualizations and embedding them into your own plugin](https://www.elastic.co/blog/developing-new-kibana-visualizations)** > > Creating custom Kibana visualizations got much easier as well as embedding them in your own plugins. However things are a bit in flux atm, so things might already change since this blog post, but it still quite close to what we have today. quick question to your answer above: `$scope.vis.params` should give you access to your visualization parameters ... and calling `$scope.vis.updateState()` will reload visualization with your changes to vis.params hope this helps, best regards ---
**Author:** ![Dan\_Crooks](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_crooks/32/42266_2.png) [@Dan\_Crooks](https://discuss.elastic.co/u/Dan_Crooks)\ **Post date:** [January 30, 2019, 4:57pm UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208/5 "2019-01-30T16:57:02Z")
Thanks. The blog was helpful, but it still uses the `vis.params` example. I was able to get it to work by using `editorState.params` in the HTML file. Thanks for the info on the angular visualizations. Most of our custom visualizations are angular. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 27, 2019, 4:57pm UTC](https://discuss.elastic.co/t/what-happened-to-editablevis/166208/6 "2019-02-27T16:57:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.