docstr: Controls persistence of some user-driven changes to the trace:
  `constraintrange` in `parcoords` traces, as well as some
  `editable: true` modifications such as `name` and
  `colorbar.title`. Defaults to `layout.uirevision`. Note that
  other user-driven trace attribute changes are controlled by
  `layout` attributes: `trace.visible` is controlled by
  `layout.legend.uirevision`, `selectedpoints` is controlled by
  `layout.selectionrevision`, and `colorbar.(x|y)` (accessible
  with `config: {editable: true}`) is controlled by
  `layout.editrevision`. Trace changes are tracked by `uid`,
  which only falls back on trace index if no `uid` is provided.
  So if your app can add/remove traces before the end of the
  `data` array, such that the same trace has a different index,
  you can still preserve user-driven changes if you give each
  trace a `uid` that stays with it as it moves.
  
  The 'uirevision' property accepts values of any type
  
  Returns
  -------
  Any
docstr_tok: ["Controls","persistence","of","some","user-driven","changes","to","the","trace",":","`","constraintrange","`","in","`","parcoords","`","traces",",","as","well","as","some","`","editable",":","true","`","modifications","such","as","`","name","`","and","`","colorbar.title","`",".","Defaults","to","`","layout.uirevision","`",".","Note","that","other","user-driven","trace","attribute","changes","are","controlled","by","`","layout","`","attributes",":","`","trace.visible","`","is","controlled","by","`","layout.legend.uirevision","`",",","`","selectedpoints","`","is","controlled","by","`","layout.selectionrevision","`",",","and","`","colorbar",".","(","x|y",")","`","(","accessible","with","`","config",":","{","editable",":","true","}","`",")","is","controlled","by","`","layout.editrevision","`",".","Trace","changes","are","tracked","by","`","uid","`",",","which","only","falls","back","on","trace","index","if","no","`","uid","`","is","provided",".","So","if","your","app","can","add\/remove","traces","before","the","end","of","the","`","data","`","array",",","such","that","the","same","trace","has","a","different","index",",","you","can","still","preserve","user-driven","changes","if","you","give","each","trace","a","`","uid","`","that","stays","with","it","as","it","moves",".","The","'uirevision","'","property","accepts","values","of","any","type","Returns","--","--","--","-","Any"]
code: def uirevision(self):
      """
      Controls persistence of some user-driven changes to the trace:
      `constraintrange` in `parcoords` traces, as well as some
      `editable: true` modifications such as `name` and
      `colorbar.title`. Defaults to `layout.uirevision`. Note that
      other user-driven trace attribute changes are controlled by
      `layout` attributes: `trace.visible` is controlled by
      `layout.legend.uirevision`, `selectedpoints` is controlled by
      `layout.selectionrevision`, and `colorbar.(x|y)` (accessible
      with `config: {editable: true}`) is controlled by
      `layout.editrevision`. Trace changes are tracked by `uid`,
      which only falls back on trace index if no `uid` is provided.
      So if your app can add/remove traces before the end of the
      `data` array, such that the same trace has a different index,
      you can still preserve user-driven changes if you give each
      trace a `uid` that stays with it as it moves.
  
      The 'uirevision' property accepts values of any type
  
      Returns
      -------
      Any
      """
      return self["uirevision"]
  
imports: from plotly.basedatatypes import BaseTraceType
  import copy
label_desc: Use image node_id 33 for calling the Indicator obj's underlying member method code with example usage: obj.uirevision() and returns: self