It would be great if we can keep the app available even if it is not supported.
If the app is going to be discontinued, is there any chance to add an option to set the name without the semantic phrases since it will not be possible to update them anymore. At least this way we can generate the periods ahead of time before the app is disabled.
After play ground a bit long with this, It work with single date only. What if i have an entity with Date range field (Example 21/09/2023 → 23/09/2023), do we have any way can get all those Period (21/09/2023 22/09/2023 23/09/2023) instead of just 1 variable: 21/09/2023 ?
I wanna the results like this: each days in date range can be linked ! Not only days, The week, the month, the quarter, the year should be displayed if it’s different with the start date in date range @Chr1sG
We got some useful feedback from those who experimented with the custom app, but for the time being, we haven’t settled on the best way forward with respect to representation of dates/times/periods within Fibery.
As it stands, we are not continuing to make the app available, but I would be willing to share the source code in case you wanted to consider self-hosting.
Fibery itself is not self-hostable - but custom Fibery integrations apps need to live on a server of yours somewhere, because they are not part of Fibery.
@Chr1sG would it be possible to share the source code with the wider community? I have had a bunch of ideas on building a few integration apps and the more examples we have, I think the easier it gets to see how to do things.