Hi Dirk,
I’d argue it might just be very worthwhile to have functionality like that in place, yes.
As always, you’re free to open up an issue on the Axon Framework GitHub page; that’ll help for our discussion when and if to pick this up.
A part from that, the API luckily allows you to provide an expected aggregate version, although you’ve correctly noted it is not being used.
A personal Repository implementation which does leverage the expected aggregate version should thus not be to hard to achieve.
It is typically the case however that you’d only retrieve an aggregate to perform commands on it.
Taking that stance, I’d assume that performing commands on old aggregates doesn’t seem like a very likely use case.
That is very likely the reason why the post you’re referring too states that if you’re querying old aggregates, that you should introduce a query model for that.
Hope this gives you some insights Dirk.
Cheers,
Steven