Skip to content

Conversation

mlell
Copy link

@mlell mlell commented Nov 13, 2021

This disassembles a progression condition that is to be relayed and creates a new progression object using all of its properties to adress the problems in #126.

As a perspective, one might think of adding a new class, like "relayedProgression" to progressions that are relayed like this and keep the original progressor ID, session ID and call, though I do not know what it would be useful for.

The steps= argument of progressor did not match the actual number of
emitted progressions or rather the sum of their `amount=`s (there are progressions with amount=0) as well in slow_sum()
When the progression condition that is to be relayed was created with
any arguments, they need to be relayed as well when creating a new
progression object in progress_aggregator().

Fixes futureverse#126.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant