class_docstr: Interface for renderers of individual environments.
  
  Renders state of one particular step -- based only on current state.
docstr: List the additional arguments that the renderer supports (beyond maze_state and maze_action), if any.
  
  Exposing available argument options like this makes it possible to create appropriate user controls
  when controlling the renderer in interactive settings (e.g., using widgets in a Jupyter Notebook).
  
  Note:
  
  Note that the types and names of arguments returned are expected to be the same across all possible env
  configurations. What can change are the available values, which then are expected to stay the same for
  a whole episode.
  
  Example of this are drivers in a vehicle routing env. If you would like to display a detail of the driver,
  a driver_id argument can be exposed. It will always be named `driver_id` and be of the same type, but
  across different episodes, the number of drivers (i.e. allowed range of the argument) might differ. It
  will always stay fixed during a whole episode though.
  
  :return: List of renderer argument objects.
docstr_tok: ["List","the","additional","arguments","that","the","renderer","supports","(","beyond","maze_state","and","maze_action",")",",","if","any",".","Exposing","available","argument","options","like","this","makes","it","possible","to","create","appropriate","user","controls","when","controlling","the","renderer","in","interactive","settings","(","e.g.",",","using","widgets","in","a","Jupyter","Notebook",")",".","Note",":","Note","that","the","types","and","names","of","arguments","returned","are","expected","to","be","the","same","across","all","possible","env","configurations",".","What","can","change","are","the","available","values",",","which","then","are","expected","to","stay","the","same","for","a","whole","episode",".","Example","of","this","are","drivers","in","a","vehicle","routing","env",".","If","you","would","like","to","display","a","detail","of","the","driver",",","a","driver_id","argument","can","be","exposed",".","It","will","always","be","named","`","driver_id","`","and","be","of","the","same","type",",","but","across","different","episodes",",","the","number","of","drivers","(","i.e",".","allowed","range","of","the","argument",")","might","differ",".","It","will","always","stay","fixed","during","a","whole","episode","though",".",":","return",":","List","of","renderer","argument","objects","."]
code: def arguments() -> List[RendererArg]:
      """List the additional arguments that the renderer supports (beyond maze_state and maze_action), if any.
  
      Exposing available argument options like this makes it possible to create appropriate user controls
      when controlling the renderer in interactive settings (e.g., using widgets in a Jupyter Notebook).
  
      Note:
  
      Note that the types and names of arguments returned are expected to be the same across all possible env
      configurations. What can change are the available values, which then are expected to stay the same for
      a whole episode.
  
      Example of this are drivers in a vehicle routing env. If you would like to display a detail of the driver,
      a driver_id argument can be exposed. It will always be named `driver_id` and be of the same type, but
      across different episodes, the number of drivers (i.e. allowed range of the argument) might differ. It
      will always stay fixed during a whole episode though.
  
      :return: List of renderer argument objects.
      """
      return []
  
file_path: maze/maze/core/rendering/renderer.py
imports: from abc import abstractmethod, ABC
  from typing import List, Optional
  from maze.core.env.maze_action import MazeActionType
  from maze.core.env.maze_state import MazeStateType
  from maze.core.log_events.step_event_log import StepEventLog
  from maze.core.rendering.renderer_args import RendererArg
label_desc: Use image node_id 1 for calling the Renderer obj's underlying member method code with example usage: obj.arguments() and returns: list