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
Also include a script to copy existing blobs to Pure.
Local is still the primary.
Beta will keep using local disk service for Active Storage because I
think there are constraints on source IPs for the Pure cluster.
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: (58 commits)
Safari doesn't support CSS `field-sizing: content` so we can shim it for now
Hide bubbles in trays
update lexical
update lexical
Update script to deal with duplicated records
Revert "Revert "Replace House with Lexical""
Revert "Replace House with Lexical"
Update actiontext lexical
Remove trace
Update lexical
Use existing method
Update lexical
Fix merge issues
Format
Cleanup
Format
Make tests pass with action text
Don't choke when rendering commands where the card was deleted
Update lexical
Simple format excerpts in activity
...
* 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.
Yes, Platform Agent is overkill for just this but there isn't a one-size JS solution for updating both input placeholders and other HTML text and we're likely to need it later for other things like displaying platform-specific PWA prompts.
Jorge Manrubia