Yes, but calendar entries are not exactly the same things as tasks, which was the specific need you posted about. And I’m not the only one who thinks that there is no universal definition:
‘There’s probably not a consensus on what anyone “would expect [recurring tasks] to behave in normal project management tools"’
Anyway, my point was that Fibery has some technical foundations to which any solution needs to build upon.
There are things that are simply not possible in Fibery (based on its current foundations).
For example, if I create a recurring event in my Outlook calendar, I can choose to have the recurrence be indefinite (no end date) but it would not be possible in Fibery to have a indefinite number of entities in an ‘event’ database.
And since Fibery does not have array field types, a single entity cannot contain a set of 1-to-∞ date values to represent all the recurrence dates it should be associated with (and even if it could, this would not be the same as having unique entries for each date).
So … 
But putting all that aside, I can see that you commented on the post that @helloitse made, which covers this case, so I have followed her guidance and made a workspace that implements something close. Perhaps it’s useful, or can at least inspire you to figure out a solution that gets you what you need.