[WIP] Bugfix/list revisions activation suffix

[Bockit]

My previous pull request added support for the idea of an activationSuffix config option, so it didn't always have to be current. Allowing you to theoretically have many activations in one db.

What I didn't take into account was fetchRevisions. This PR adds support for activationSuffix to fetchRevisions so the current revision is derived from activationSuffix.

That has been dealt with in this PR, the WIP part is: I still haven't taken into account revision trimming with multiple activated revisions. At the moment it will trim based on your activationSuffix, so if you had activated with activationSuffix currentSpecial in the past, you could lose it in the future if you are uploading with trimming and a different activationSuffix.

Any suggestions here? You could theoretically have a key listing activation keys/suffixes but maybe there's a better way.

[Bockit]

Also whoever wrote the tests I've modified, it would be good if someone could make sure I haven't inadvertently broken something.

[ghedamat]

@Bockit sorry for the delay,

I think this is still interesting and worth finishing because if I get it correctly the current behaviour on master is partially broken (correct me if I'm wrong)

mind rebasing and then we can have another look?

[ghedamat]

@Bockit ping

[Bockit]

Yep, you're correct. I'll rebase tonight. Sorry, this got lost in all the noise.

[ghedamat]

@Bockit sorry for nudging you again.

If that's easier we could try to take this over and bring it to completion.

thanks!

[Bockit]

@ghedamat Being real about this, I doubt I'm going to get much time to work on it in the short to medium term. We don't use this at work anymore and in my own time I'm doing other things. If others want to try and take over I welcome it.

[ghedamat]

Will close for now

If the use case comes up again we can resume the work done here and take it to the finish line

thanks anyway @Bockit !

hope you this wasn't the reason for you stopping using ecd :D