As in the title, currently to log the project ID in analytics, one needs to raise ProjectIDEvent, which is then magically passed to the usage logs. Besides this being overly complicated, it makes no sense for practical reasons: project ID can be set only once per session, but what if I work on two projects in parallel?
Instead, we could simply add one more parameter to the LogUsage method, where the project ID would be set. Besides simplicity and elegance, this would also bring more flexibility, letting each of the UIs control the source and value of the ID parameter.
Description:
As in the title, currently to log the project ID in analytics, one needs to raise
ProjectIDEvent, which is then magically passed to the usage logs. Besides this being overly complicated, it makes no sense for practical reasons: project ID can be set only once per session, but what if I work on two projects in parallel?Instead, we could simply add one more parameter to the
LogUsagemethod, where the project ID would be set. Besides simplicity and elegance, this would also bring more flexibility, letting each of the UIs control the source and value of the ID parameter.