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
Element Call features the ability to generate a unique ID, and share it with other clients when generating a rageshake so that all shakes can be grouped together when debugging. I'd like it so that this would create one issue, with a sub issue for each child shake.
I suspect the best way to do this would be to introduce a standard identifier for grouping shakes, and have the code automatically append subissues to an existing issue if the ID exists. This might require trace amounts of persistence, however.
The text was updated successfully, but these errors were encountered:
Element Call features the ability to generate a unique ID, and share it with other clients when generating a rageshake so that all shakes can be grouped together when debugging. I'd like it so that this would create one issue, with a sub issue for each child shake.
I suspect the best way to do this would be to introduce a standard identifier for grouping shakes, and have the code automatically append subissues to an existing issue if the ID exists. This might require trace amounts of persistence, however.
The text was updated successfully, but these errors were encountered: