Description:
With work done in #505 drastically simplifying the workflow for assigning ProjectIds to usage logs, we should aim to compltely remove the ProjectIDEvent completely.
To do this, we need to find a way for the SetProjectId method to be able to access UI Name as well as FileId. This could potentially be done by changing this from a basic compute method into a new special component, like GetFileInfo or similar. Then, each UI can make its own implementation of the component and make sure all required data is provided, and then simply call the UpdateProjectId method in added in the PR linked above.
Some downside of adding yet another special case component, so before actioned in the way described above, should investigate if possible to be done another way.
Description:
With work done in #505 drastically simplifying the workflow for assigning ProjectIds to usage logs, we should aim to compltely remove the ProjectIDEvent completely.
To do this, we need to find a way for the SetProjectId method to be able to access UI Name as well as FileId. This could potentially be done by changing this from a basic compute method into a new special component, like GetFileInfo or similar. Then, each UI can make its own implementation of the component and make sure all required data is provided, and then simply call the UpdateProjectId method in added in the PR linked above.
Some downside of adding yet another special case component, so before actioned in the way described above, should investigate if possible to be done another way.