You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This component has been working great for normal waste collections, but it's basically useless for one particular type of waste that works different from the rest. Instead of being collected, we have to bring the waste to a specific spot quite far from my house and between specific hours. This is an exception even in the waste calendar made available by the provider where they simply put the available hours in the description.
Normally waste is collected early in the morning, so the default 10AM refresh fine works for this. But for this type you can drop it off from noon to the afternoon on the next day. Using the regular settings this means that it disappears before it has even started. Moreover, I prefer to bring it in the morning of the next day to avoid having to go in the dark. Even a simple offset would not would not work very well, because sometimes I have no choice but to bring it in on the evening of the same day. Right now I cannot use this component for the type of trash because most often it is already gone from the calendar when I want to check for it. (Another idea here: keep the previous event of each type available in the calendar)
The issue is somewhat similar to #679 , but those are fixed hours and not exactly what I would prefer. Ideally I can configure a start time and a total duration that can span multiple days. I would not mind making a pull request or even modifying the aforementioned one, but first I'd like some feedback. I want a proper solution that can be merged so I can simply update the component instead of having to use a personal fork.
The text was updated successfully, but these errors were encountered:
The current implementation uses Date objects not DateTime object for every internal handling. I think Dates should keep the default behavior, maybe there could be a configuration option to use some kind of DateTime range, if the Source supports this: The source may return some kind of DateTime range instead of Date events and if this option is enabled the calendar shows this range.
This implementation probably needs some bigger changes and @mampfes should probably take a look first
I propose a feature for:
The integration in general
Describe your wanted feature
This component has been working great for normal waste collections, but it's basically useless for one particular type of waste that works different from the rest. Instead of being collected, we have to bring the waste to a specific spot quite far from my house and between specific hours. This is an exception even in the waste calendar made available by the provider where they simply put the available hours in the description.
Normally waste is collected early in the morning, so the default 10AM refresh fine works for this. But for this type you can drop it off from noon to the afternoon on the next day. Using the regular settings this means that it disappears before it has even started. Moreover, I prefer to bring it in the morning of the next day to avoid having to go in the dark. Even a simple offset would not would not work very well, because sometimes I have no choice but to bring it in on the evening of the same day. Right now I cannot use this component for the type of trash because most often it is already gone from the calendar when I want to check for it. (Another idea here: keep the previous event of each type available in the calendar)
The issue is somewhat similar to #679 , but those are fixed hours and not exactly what I would prefer. Ideally I can configure a start time and a total duration that can span multiple days. I would not mind making a pull request or even modifying the aforementioned one, but first I'd like some feedback. I want a proper solution that can be merged so I can simply update the component instead of having to use a personal fork.
The text was updated successfully, but these errors were encountered: