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
The depsolve api call which provides all packages needed for the recipe, labeled as 'dependencies'. These contents are then displayed as the dependencies, but currently the selected components are included in this list that displays as dependencies.
Component (web, API, etc)
web
How often reproducible
Whenever depsolve successfully returns a list of dependencies.
Steps to Reproduce
Navigate to the recipe or edit recipe page.
Note which components are listed in the Selected Components section
search for one of the 'modules' in the list of 'dependencies'
Actual results
The api call returns all components in the list of 'dependencies'.
The front-end js does not currently filter out the selected components from that list.
Expected results
The api call returns all components in the list of 'dependencies', as expected.
Then the front-end js filters out the selected components from that list.
Additional info
Additionally, the UI indicates that the list of dependencies is the first-level. But really, these are the total number of dependencies. Additional discussions are needed to determine whether we should show just first level vs all vs something else. But it would be nice to have the UI at least accurately describe the contents being listed.
The text was updated successfully, but these errors were encountered:
Description of problem
The depsolve api call which provides all packages needed for the recipe, labeled as 'dependencies'. These contents are then displayed as the dependencies, but currently the selected components are included in this list that displays as dependencies.
Component (web, API, etc)
web
How often reproducible
Whenever depsolve successfully returns a list of dependencies.
Steps to Reproduce
Alternatively:
Actual results
The api call returns all components in the list of 'dependencies'.
The front-end js does not currently filter out the selected components from that list.
Expected results
The api call returns all components in the list of 'dependencies', as expected.
Then the front-end js filters out the selected components from that list.
Additional info
Additionally, the UI indicates that the list of dependencies is the first-level. But really, these are the total number of dependencies. Additional discussions are needed to determine whether we should show just first level vs all vs something else. But it would be nice to have the UI at least accurately describe the contents being listed.
The text was updated successfully, but these errors were encountered: