You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because each folder in a path must be defined as individual Directory elements, Directory elements provide the highest chance of conflict in setup authoring. That often leads teams to centralize the Directory elements in one (or a couple) files to prevent the conflicts. That leads to merge conflicts when different developers edit those few files.
All of this can be avoided if Directory elements are allowed to be duplicated. When combined with feature 4258, limiting this feature to private identifiers prevents the undesirable side effect where one DirectoryRef could pull in many Fragments.
Originally opened by firegiantco
The text was updated successfully, but these errors were encountered:
Because each folder in a path must be defined as individual Directory elements, Directory elements provide the highest chance of conflict in setup authoring. That often leads teams to centralize the Directory elements in one (or a couple) files to prevent the conflicts. That leads to merge conflicts when different developers edit those few files.
All of this can be avoided if Directory elements are allowed to be duplicated. When combined with feature 4258, limiting this feature to private identifiers prevents the undesirable side effect where one DirectoryRef could pull in many Fragments.
The text was updated successfully, but these errors were encountered: