Repository navigation
0.12.0
·
216 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Changed
- The monthly recap shows your badge art. Each member's badges in the recap now get a line naming them and a row of the same art the badge posts use, beneath it. The line names up to 10 badges, one row's worth, and counts the rest ("and 2 more badges"). A badge whose art isn't in Slack keeps its text tag, and when there's no art at all, such as when the Slack app lacks the
files:writescope, the recap is the text it was, with 6 badges a member. The recap waits for, retries, and falls back from the art the same way badge posts do. - Badges are listed rarest first. Badge posts and the recap list each member's badges by tier, highest first (Diamond, Gold, Silver, Bronze, First), then by ladder (Rare, then Occasional, then Frequent), then in the order of the badge table. Before, they followed the badge table alone, so a Diamond could be cut off ("and 6 more badges") while a First tier was named. A list cut short now leaves off the most common badges.
- Clearer failures (#153). The banner at the top of the page now says why a tap didn't save: "Not saved. Check your connection and try again." with no network, "Not saved. Something went wrong. Try again." after a server error, and "Not saved. Reload the page." when your session has expired. A request with no answer after 15 seconds gives up and says it might not have saved. Before, every failure said "Not saved. Reload the page.", and a stalled request left the button waiting with no end. A preference row that didn't save goes back to the level it last saved, and the banner stays until each card or row that failed saves, or that card refreshes.
- An error on a call card scrolls into view (#153). When a call refuses a tap, such as one that lost a race, its error at the top of the card now scrolls into view instead of staying above the screen on a tall card. With reduced motion, it jumps there without scrolling smoothly.
- A tap shows at once (#153). Buttons, preference levels, and chips now darken or lighten the moment you press them, instead of showing nothing until the save comes back, and their text keeps its contrast in both themes. A pressed chip that links shows its border. With motion allowed, a pressed control also shrinks slightly, and colors ease over about a tenth of a second, so a choice you change on a call card, such as In or I can cook, eases into place. A card's refresh that changes nothing moves nothing. With reduced motion, every change is instant.
- A slow save shows that it's working (#153). When an answer, vote, or preference takes longer than 150 milliseconds, the control you tapped dims and the pointer shows progress until it saves. A save that's faster than that shows nothing, so a quick tap doesn't flicker, and a card's refresh never dims it. Screen readers hear the card or row as busy until the new one arrives.
- A full-page form posts once (#153). Forms that load a new page, such as How was it? and Fun mode, dim their buttons while they post, and a second tap or click is ignored, so a double tap no longer posts twice. If you go back to the page, or the next page doesn't load within 10 seconds, such as when you stop it, the form works again. A form that isn't sent, because a field is missing or a catalog file is too big, isn't affected, and neither is one you send with Ctrl, Cmd, or Shift held, which can open the result in another tab or window.
- "Saved" fades on Preferences (#153). The "Saved" beside a preference you change now fades after about 2 seconds, instead of staying on every row you changed. With reduced motion, it disappears without fading. Screen readers can still read it.
Removed
- The upgrade guard for old feedback forms (#148). 0.11.0 refused a How was it? form or modal opened before the upgrade, which still asked about the food and the place, so that saving it couldn't take back your rating. Both instances now run 0.11.0, so the guard is gone. A rating is now simply required: the web form and the Slack modal always send one, because a rating, No answer at first, is always selected. A web post without one gets the Request refused page, a Slack modal without the rating closes, and one with no rating picked says "Pick a rating, or No answer." None of them saves anything.
Fixed
- The last tap is the one that sticks (#153). On a call card, tapping Maybe and then Out before the first answer came back saved Out but showed Maybe. On Preferences, tapping +1 and then +2 in the same row saved and showed +1. Now a tap on another choice replaces one still on its way, so the card or row shows and saves your last choice, and the replaced tap raises no error. A double tap on the same button sends it once: a double click on Invite no longer invites the guest twice, and +15 min no longer moves the deadline twice.
- Focus stays on what you tapped (#153). After you answer, vote, or change a preference, keyboard focus stays on that button or level instead of jumping to the top of the page, so the arrow keys keep moving through a preference's levels.
- Open calls keep refreshing (#153). With three or more open calls on Today, the middle cards' refreshes were dropped, and a refresh that answered after a tap could undo what the tap showed. Now each card refreshes on its own, a tap replaces a refresh in flight, and a refresh never starts while a tap is saving. A card skips its refresh only while you type in one of its fields or have one of its forms open, not just because a button in it has focus, and a refresh no longer dims the card's buttons.
- Notices on History and the Catalog show in what you land on (#153). After you save feedback, log a meal, or edit one, History scrolls to that meal, and after you add or edit a catalog item, the Catalog scrolls to it. Their notices, such as "Thanks for the feedback!" and "Changes saved.", were off screen at the top of the page. A notice now shows inside the meal or item, and the entry is highlighted for a moment and then fades. With reduced motion, the highlight stays and nothing moves. "Meal deleted." has no meal to land on, so it stays at the top, as does a notice whose meal or item isn't on the page, such as an item you deactivated. Any page that scrolls to something, such as History, the Catalog, or a row on Preferences, no longer hides it under the sticky top bar, or under the test instance's banner.
- Badge icons no longer drop to text when one new badge's art fails to upload. When a post needed art for a new badge tier and the upload failed or took longer than 3 seconds, every badge after it, in alphabetical order by badge, showed as text, even if its art was already in Slack. Art uploaded earlier in the same post was dropped too. Now only the badge whose upload failed shows as text. This affects badge posts, the recap, and App Home.
- Forgotten badge art uploads again in the background. When Slack refuses badge art and Dinnerbell forgets the files,
dinnerbell servestarts uploading the missing tiers again in the background, as it does after startup, so the next post doesn't wait for them. - A History or Catalog page that isn't a number shows the first page. An address such as
/history?page=abcor/catalog?q=thai&page=2.5showed Request refused. It now shows the first page, and the Catalog keeps your search. A page number past either end still shows the nearest page. - A correction after the meal moves the count and the badges (#162). When an admin corrects who cooked, picked up, or ordered after a meal is done, the meal's count for that role now moves to the person who has it. They earn any badge the count reaches, announced like any other and celebrated by the den. The person who lost the role loses each badge tier their counts no longer reach on the current counts, even a tier first earned at a lower count before an admin raised it. A pending one is never announced or celebrated. One already announced leaves Stats, App Home, the household's newest badges, and future recaps; a post already sent or queued in Slack stays. Correcting it back restores both. Each correction that moves a count is audited as
event.contributions_recounted, with the badges taken back and awarded. Before, a correction after done changed the record but not the counts. The fix isn't retroactive: a call corrected before this release keeps its old counts. To bring one up to date, correct its role again, for example set it to nobody and then back to whoever did it.
Upgrade notes
- Badges: revision
0024_badge_award_autoincrementrebuilds the badge award table on the first start, keeping every award, so the ID of a badge taken back is never given to another. It also starts new IDs above every member's den marker (fun_seen_award), so no new badge goes uncelebrated. To go back to 0.11.0, restore the backup you took before the upgrade.
Image
ghcr.io/dsmorgan/dinnerbell:0.12.0@sha256:cf41228bbfae27c3d1edc267596c4f8eeaa09ec4e2a3e98d7f03d9cceb48bcc5