Currently, the identifier passed when adding parts or views to the WorkbenchLayoutFactory is used as the alternativeId rather than the technical part/view ID (unless prefixed with part. or view.). This leads to confusion when accessing the part/view via WorkbenchService, e.g., to activate it.
Instead, the API should be changed to only accept the technical id. The alternativeId, or better secondaryId can still be passed via options.
Currently, the identifier passed when adding parts or views to the
WorkbenchLayoutFactoryis used as thealternativeIdrather than the technical part/view ID (unless prefixed withpart.orview.). This leads to confusion when accessing the part/view viaWorkbenchService, e.g., to activate it.Instead, the API should be changed to only accept the technical id. The
alternativeId, or bettersecondaryIdcan still be passed via options.