Is there a way to NOT persist the occurrences? and just somewhat generate them based on a date range instead?

[jfrux]

Trying to find a way to build out a calendar UI that isn't constantly creating records just so it can show them to the user. Or am I missing something? Or does it only persist them if you want them persisted?

Sorry!

[rexblack]

Persisting occurrences is intended to come on top of the creation of the schedule. You can access all calculated occurrences as described in "Accessing IceCube" without the need of persisting stuff, but then have to take care of what to do with them by yourself. Meaning that currently you won't be able to list them up like you're used to do with database records.
This is something i always wanted to improve on. Ideally you could deal with the occurrences as if they were persisted. That would make everything far more easy to maintain and probably also to adapt to certain use cases. But i didn't manage to do it so far and - i'm so sorry - currently i'm so f*****g busy and it's really a pity that i cannot take care of this gem now. Hopefully this is going to change very soon.

Sorry! ;-)

[jfrux]

Duuuuude don’t you worry about it! Thank you so much for your response. I have this working without persisting but it’s sadly without your gem. Would love to pull it down for a bit and see if I could get it working with the gem but I’m kind of in the same boat as you of course! Keep doing what you do! Cheers mate!

…

On Mar 29, 2018, 5:38 AM -0400, Rafael Nowrotek ***@***.***>, wrote: Persisting occurrences is intended to come on top of the creation of the schedule. You can access all calculated occurrences as described in "Accessing IceCube" without the need of persisting stuff, but then have to take care of what to do with them by yourself. Meaning that currently you won't be able to list them up like you're used to do with database records. This is something i always wanted to improve on. Ideally you could deal with the occurrences as if they were persisted. That would make everything far more easy to maintain and probably also to adapt to certain use cases. But i didn't manage to do it so far and - i'm so sorry - currently i'm so f*****g busy and it's really a pity that i cannot take care of this gem now. Hopefully this is going to change very soon. Sorry! ;-) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.