- Introduces a distinct controller and individual forms for each option so they behave like other pop-ups
- Adds `filter` and `navigable-list` behaviors
* main:
`event.assignees` collection doesn't include `event.creator` when self-assigning
Consistent verb forms
Autolinking shouldn't include final punctuation.
dep: update kamal to edge
No need to delegate auto_closing? anymore
Extract common method to query when entropy is cleaned
Invalidate card caches when editing workflows
# Conflicts:
# app/javascript/controllers/navigable_list_controller.js
Later on we could consider adding an explicit button that only shows up when the filter has no matches and there is something typed in the filter input
* main: (25 commits)
Add controller to retarget links
Use more complete regexp
dep: bundle update
refactor: Extract a Card::Entropy concern
Autolink emails and URLs at rendering time
Remove the "mirror" storage service
Update production storage to write to the Pure blob store
Clean up the purestorage config, and add explanatory comments.
Drop the action_text_markdowns table
Mount mission control under `/admin/jobs`
dep: add mission_control-jobs
Flip the storage mirror to write to Pure as the primary
Production mirrors Active Storage to `:purestorage`
Make sure Sentry is configured for the beta env.
Update lexical
update lexical
update lexical
Create a distinct "beta" environment
Revert "Patch for cards missing description"
Add a kamal "ssh" alias
...
- Make them navigable by keyboard (UP, DOWN, ENTER to activate option).
- Filter based on the actual text in the element, use containment condition instead of CSS selector on value prefix.
- Make all the elements in the filter searchable and reachable by keyboard.
to encompass behavior related to auto-closing and auto-reconsidering.
Note that putting this code in a single place reveals an asymmetry
between the actions:
- Auto-closing period is an optional attribute of a collection
- Auto-reconsidering period is hard-coded to 30 days for all collections
The problem was that after redirecting back with morphing, the autosave mechanism
would trigger an autosave call with an empty content.
This is a first patch. The editor shouldn't be triggering these "change" events
in the first place when loading the editor.
* main:
Don't choke when rendering commands where the card was deleted
Update tests
Rework system events
test: add missing assertions
dep: bump active_record-tenanted to fix URI support
Remove hyphen from "Un-do"
Prevent default when handling keyboard shortcuts
dep: update AR::Tenanted to support database URIs
Detect platform and label the correct hotkey shortcut
Things got too tight
Don't require TLS for Beamer at the moment
dep: update dependencies
# Conflicts:
# Gemfile
# Gemfile.lock
# app/assets/stylesheets/comments.css
- Restyle system events so they don't look like comments and aren't attributed to the system user
- Ensure the event creator is included in the description so it's clear who did it.
- Walk back system comment replacement. Yes, it potentially avoids embarassing people when they change their mind, it's also losing data. If two intentional assigments happen in proximity, we've been only showing the latest one,.
Without this, any default action would still happen. With Chrome on
Linux, that causes browser features to be triggered with our CTRL+J and
CTRL+K actions.
Jason Zimdars