Actions, goals, prioritisations spread over multiple bases can not be viewed in one place. Which breaks the purpose of having a unifiable actions list and unifiable prioritisations list & "gantt" like view.
Description (acceptance criteria)
Allow the user to specify additional bases to load all the components from
Will require #207.
[ ] Add a load_other_base_ids: string[] to KnowledgeBase
[ ] Add UI in the base edit page to set / edit these
[ ] When a base loads, after it has loaded its own components, it also loads the components of the other bases into specialised_objects.wcomponents_by_id_from_other_bases
Why (hypothesis)
Once #205 is complete, this addition will allow the user to view actions and prioritisations over all their bases.
Will allow for a more seamless loading of components referencing other bases, e.g. if you have a base with 100 components which are from a different base (e.g. base no 12), then instead of having to trigger the components to load when a view requires them they could be loaded all at start.
Will enable future changes to allow people to "fork" other knowledge bases: they can load all of another user's base into their own, add (or copy) all the components they want to reference, then optionally remove the other user's base from loading all the components.
Why not
Alternative solution for seeing all actions and prioritisations over all of a users bases is to extend the functionality in #205 to fetch any action, goal or prioritisation across all the bases a user has access to. But then I could imagine a user wanting to specify "all the bases except the following old project bases", and then later: "only the following 10 active bases".
Currently
Description (acceptance criteria)
Allow the user to specify additional bases to load all the components from Will require #207.
specialised_objects.wcomponents_by_id_from_other_basesWhy (hypothesis)
Why not