Skip to content

Settings and activity

3 results found

  1. 1,472 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Hare supported this idea  · 
  2. 123 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Hare supported this idea  · 
  3. 737 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    John Hare supported this idea  · 
    An error occurred while saving the comment
    John Hare commented  · 

    Yes please implement this critical piece, to keep improving a brilliant application.

    The specific problem I am addressing is building a family of tabbed dialogs where the tabs need to renamed for the specific use case. Whereas master components allows editing of items shared by all states once we are forced to create an instance each edit needs to be repeated for every state - a time-consuming and error prone process. My own preference would be for two levels of inheritance:
    1 - edits made to the default state ripple though all other states unless explicitly overwritten
    2 - genuine duplication of a master component to create a fully separated branch of the tree

    Regards