William Grant
|
89c70760a5
|
fix: refactor and works for all legacy test cases, modern to modern is broken
|
2 years ago |
|
William Grant
|
6dd340ca6c
|
feat: handle legacy disappearing messages more gracefully due to protobuf issues
added utility function for checking for undefined properties on a protobuf, renamed expireTimer to expirationTimer in some places
|
2 years ago |
|
William Grant
|
4c4bc045d7
|
fix: renamed ExpirationType enum value LEGACY to UNKNOWN
|
2 years ago |
|
William Grant
|
2338058b3e
|
fix: make sure expirationType and expireTimer are defined after v2 is released
|
2 years ago |
|
William Grant
|
61b91e2485
|
fix: make sure migration triggers with the correct date for current development
|
2 years ago |
|
William Grant
|
df40ff8855
|
feat: added legacy to the ExpirationType enum in the protobuf and updated support
the desktop protobuf implementation doesnt support undefined for optional enum values this is a known bug.
|
2 years ago |
|
William Grant
|
b8ab952c33
|
fix: explicitly set expirationType to undefined if sending a legacy message
|
2 years ago |
|
William Grant
|
bddc018ce7
|
fix: updated featureReleaseTimestamps for testing purposes
|
2 years ago |
|
William Grant
|
99412beaf3
|
feat: added dismiss button to NoticeBanner
|
2 years ago |
|
William Grant
|
2f4c0114aa
|
feat: tested new expiration modes with legacy and new clients
fixed banner logic
|
2 years ago |
|
William Grant
|
93cb972514
|
feat: updated hasOutdatedClient to track last user to send a legacy message
this makes the banner work properlly in closed groups
|
2 years ago |
|
William Grant
|
84dec94450
|
fix: cleanup logging
|
2 years ago |
|
William Grant
|
dc57454911
|
feat: ignore conversation settings when new modes are unlocked
|
2 years ago |
|
William Grant
|
718986c416
|
fix: improved feature release logic
|
2 years ago |
|
William Grant
|
ea0a505dcf
|
fix: fixed state of overlay options depending on release status
|
2 years ago |
|
William Grant
|
15c054a35e
|
feat: added ability to reset the releaseFeature logic by updating the featureReleaseTimestamp
|
2 years ago |
|
William Grant
|
80f18e9f1c
|
feat: use correct timer options and set the defaults
|
2 years ago |
|
William Grant
|
6de7c5c405
|
fix: legacy message checks must look for the ExpirationTimerUpdate flag explicitly
use correct model for a message in a closed group
|
2 years ago |
|
William Grant
|
854742c0b1
|
fix: improved logic for turning off disappearing messages
|
2 years ago |
|
William Grant
|
a3a0c3f9de
|
feat: fixed closed groups legacy mode
|
2 years ago |
|
William Grant
|
8117e631d0
|
feat: legacy mode now works for 1-1 chats
|
2 years ago |
|
William Grant
|
03bc6706f6
|
feat: added legacy mode timer notification copy
|
2 years ago |
|
William Grant
|
349b513051
|
fix: only log errors when syncing an expire timer message and not all sync messages
|
2 years ago |
|
William Grant
|
6f1230398c
|
fix: TimerNotification text is now centered
|
2 years ago |
|
William Grant
|
d698f66d50
|
feat: updated clients can send ExpirationTimerUpdateMessages to older clients
fixed syncing of ExpirationTimerUpdateMessages
|
2 years ago |
|
William Grant
|
75f1b5ed65
|
fix: left align PanelRadioButton text
|
2 years ago |
|
William Grant
|
bd900128f4
|
feat: added hasOutdated Client to convo model, use feature release check to process disappearing messages
trigger banner when receiving a legacy disappearing message via hasOutdatedClient
|
2 years ago |
|
William Grant
|
e81ac0a847
|
feat: updated NoticeBanner style
|
2 years ago |
|
William Grant
|
7fae5344f4
|
fix: include off in available modes in call cases
|
2 years ago |
|
William Grant
|
4dbbada728
|
feat: added notice banner component
show notice when conversation is in legacy mode, extracted some UI components from the ConversationHeader, updated featureReleaseTimestamp
|
2 years ago |
|
William Grant
|
93005d32d8
|
feat: updated db migration to support legacy mode
|
2 years ago |
|
William Grant
|
848c97938c
|
feat: disabled new disappearing message modes behind a timed feature release function
|
2 years ago |
|
William Grant
|
190c68d759
|
feat: added disabled state to right panel components
|
2 years ago |
|
William Grant
|
255b6225c9
|
feat: block sending disappearing messages of the wrong type in different conversations,
improved disappear after send or read logic, disable legacy sending for now
|
2 years ago |
|
William Grant
|
7d0673f7f2
|
wip: added new legacy mode to panel, improved backwards compatibility
legacy mode support in conversation header, added typing for the expireUpdate, next is sending support
|
2 years ago |
|
William Grant
|
190357b006
|
fix: cleanup
|
2 years ago |
|
William Grant
|
12087da2be
|
fix: repaired closed group disappearing messages
|
2 years ago |
|
William Grant
|
42356b0d60
|
fix: duplicate timer update messages
|
2 years ago |
|
William Grant
|
97ecc9e521
|
feat: fixed double expiration update message issue
started creating an inheritable expiration message class, improved start triggering logic
|
2 years ago |
|
William Grant
|
446752cf54
|
feat: DataExtractionNotifications now expire
MessageRequestResponses should not expire, pass yarn ready
|
2 years ago |
|
William Grant
|
5c697572a7
|
feat: Call Notifications now expire properlly
include the direction in the expiration props, setting the start timer doesnt directly update the model
|
2 years ago |
|
William Grant
|
f122c206da
|
fix: improved backwards compatibility
|
2 years ago |
|
William Grant
|
ac844af691
|
feat: updated timer notification design and copy
|
2 years ago |
|
William Grant
|
307fefcedc
|
feat: improved sender disappear after reading time
|
2 years ago |
|
William Grant
|
4ef3537a53
|
feat: timer notifications expire correctly when disappearing after sending
|
2 years ago |
|
William Grant
|
f36bbb9c7c
|
feat: group invitiations now disappear
|
2 years ago |
|
William Grant
|
2d6d6b4134
|
feat: moved PropsForExpiringMessage to state ducks
|
2 years ago |
|
William Grant
|
07af0dfe0e
|
fix: remove unneeded SyncedExpiries type from the Protobuf
|
2 years ago |
|
William Grant
|
513f94cb25
|
feat: extracted expiry logic from the GenericReadableMessage to a new component
This allows use to use the expiry logic for different visible messages not just generic ones
|
2 years ago |
|
William Grant
|
e34e3d4a4b
|
fix: resolved some yarn ready issues
|
2 years ago |