Making a release of my studio project a possible dependency

Context :

Given a Studio project A with some dependencies, and a release R of this project.
As a user, I want release R to be visible and shared with other users, such that they can use the release (including implicit dependencies) in their project.  

 

As such, I want to be able to add a Studio Project to my App Definition. In doing so, have clear visibility of the elements that are brought in my that Studio project. 

 

To Do :

 Wireframes -> https://nuxeo.invisionapp.com/console/AppDef+ReleasesTags_UI-Design-ckqqoidyn0esm015c4iahgmeu/ckqqoifvh0eni014icepz2gc8/play

 

The user should find all Studio projects, add-ons etc. that he has access to in app def 

-> Remove the filter that filters out studio projects in app def

The search bar will remain as it is now, it should not be possible to add a project to itself, the platform compatibility checks should occur as they do now on the first level only.   

 

-> On 'Save' the items added to the project will be displayed as blocks beneath this is search bar 

-> The Current Add/Remove section will be maintained as changes are made to the search bar (second second screen in link)

-> Transitive/implicit dependent projects and add-ons will be display as blocks in the list, but not in the search bar. All elements in the search can be deleted, the blocks are read only.    

 

Inaccessible dependencies 

 

> We allow all accessible (first-level) add-ons and studio projects to be added to a project (because of access right, or platform version errors and the likes) 

> If an inaccessible implicit/transitive dependency is found in the item added, the user will receive a warning validation error, after 'Save'  

"The current project cannot access dependency project X, which is a dependency of package Y.   

Package Y will still be installed without dependency package X.

Please be aware that some features may not function as intended by the package author.

Please contact your administrator or the package owner to establish access"  

  

Blocks

 

Blocks will need to include the following information 

• Package Title 
• If transitive/implicitly -> Originating package 
• Version
• Owner 
• If the package has dependencies, a list of these with versions 
• Short Description
• A clickable link to the Package's Marketplace Page 
• Wether the package or any dependency are locked 

 

Other considerations :

 

• We are not putting this feature behind a feature flag 

• The Wrapper solution is not planned for M2, but could be an option at a later date

 

AC:

• I can add Studio projects I have access to my project via App Def, excluding my own project
• I clearly see in App Def block for all direct and implicit dependencies with enough information for me to understand the package name and the links between packages
• A link beside the package name allows me to view it in the marketplace. 

• Addition very late = Nuxeo Users only