-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completed scheduled maintenance should appear in timeline #93 #117
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we should create Data Objects for this, and merge the incidents / schedules into each other before displaying then. Pairing this with #107 would make things a lot more consistent between the two types of data too.
@empty | ||
<div class="text-zinc-500 dark:text-zinc-400 text-center"> | ||
{{ __('No incidents reported between :from and :to.', ['from' => $from, 'to' => $to]) }} | ||
@foreach ($incidents as $date => $incident) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this, I think that if incidents are empty, but schedules aren't, then nothing will show.
@steffjenl schedules have just had a refactor to now determine their status based on the |
* main: (61 commits) Use null safe op instead of optional helper Remove unused ProfileUpdateRequest form request Remove unused method Fix variable Add return type Fix bad resource relation Fix code styling Schedule status doesn't need to be defined manually Allow creating schedule updates from table view Add logout button to status page Don't add `autocomplete` to `TextColumn` Compile Assets Update DEPENDABOT.yml Use Node 22 when building assets Use PHP 8.3 when compiling assets Fix docblock Fix code styling Scheduled Maintenance Updates (cachethq#109) Fix ordering of incident timeline within a day Improve incident API ...
@steffjenl I've merged |
@steffjenl do you still have any appetite to get this merged or shall I look into it separately? I'd love for this to be your contribution. |
@jbrooksuk can you look to this PR, Because Data Objects is not ready I have created an solution for the different types of objects for now.