IntenseWebs/discourse
3
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2026-08-09 12:38:21 -05:00
Code Issues Packages Projects Releases Wiki Activity
51,494 Commits 956 Branches 574 Tags
d5e8bd790b95d794c16783a095ffc1d3e8a9b259
Commit Graph
15 Commits
Author SHA1 Message Date
Jarek Radosz 8421327845 DEV: Format UserStatus#ends_at as a ISO8601 timestamp (#23796) 
…as we do when publishing a mesage bus update: https://github.com/discourse/discourse/blob/07c93918ecbc82cda6cd9a079f27cfed432bcb7e/app/models/user.rb#L871-L871
 2023-10-05 20:41:12 +02:00
David Taylor 4d12bdfdcb DEV: Fix user_status_controller_spec flakiness (#20083) 
In some situations, these HTTP calls would cause some cache to warmup and send a `/distributed_hash` message-bus message. We can avoid tracking those by passing a specific channel name to `track_publish`.
 2023-01-30 22:42:47 +00:00
David Taylor fa7f8d8e1b DEV: Update user-status test to assert message-bus channels (#20068) 
This test appears to be flaky. This assertion should help us track down the reason.
 2023-01-30 13:54:44 +00:00
Bianca Nenciu 23a74ecf8f FIX: Truncate existing user status to 100 chars (#20044) 
This commits adds a database migration to limit the user status to 100
characters, limits the user status in the UI and makes sure that the
emoji is valid.

Follow up to commit b6f75e231c.
 2023-01-30 10:49:08 +02:00
Bianca Nenciu b6f75e231c FIX: Limit user status to 100 characters (#20040) 
* FIX: Limit user status to 100 characters

* FIX: Make sure the emoji is valid
 2023-01-27 16:32:27 +02:00
David Taylor cb932d6ee1 DEV: Apply syntax_tree formatting to spec/* 2023-01-09 11:49:28 +00:00
Andrei Prigorshnev 6357a3ce33 FEATURE: User Status API (#19149) 
This adds API scope for the user status. This also adds a get method to the user status controller. We didn't need a dedicated method that returns status before because the server returns status with user objects, but I think we need to provide this method for API clients.
 2022-11-24 19:16:28 +04:00
Phil Pirozhkov 493d437e79 Add RSpec 4 compatibility (#17652) 
* Remove outdated option

https://github.com/rspec/rspec-core/commit/04078317ba6577699d06cf4dccf014254dcde7a6

* Use the non-globally exposed RSpec syntax

https://github.com/rspec/rspec-core/pull/2803

* Use the non-globally exposed RSpec syntax, cont

https://github.com/rspec/rspec-core/pull/2803

* Comply to strict predicate matchers

See:
 - https://github.com/rspec/rspec-expectations/pull/1195
 - https://github.com/rspec/rspec-expectations/pull/1196
 - https://github.com/rspec/rspec-expectations/pull/1277
 2022-07-28 10:27:38 +08:00
Andrei Prigorshnev ef923f1bb1 FEATURE: Publish everyone's status to everyone (#17343) 2022-07-07 17:37:05 +04:00
Andrei Prigorshnev c59f1729a6 FEATURE: auto remove user status after predefined period (#17236) 2022-07-05 19:12:22 +04:00
Andrei Prigorshnev 033f72c65f FEATURE: user status emoji (#17025) 2022-06-22 18:15:33 +04:00
Alan Guo Xiang Tan f618fdf17f Revert "DEV: Centralize user updates to a single MessageBus channel. (#17058)" (#17115) 
This reverts commit 94c3bbc2d1.

At this current point in time, we do not have enough data on whether
this centralisation is the trade-offs of coupling features into a single
channel.
 2022-06-17 12:24:15 +08:00
Alan Guo Xiang Tan 94c3bbc2d1 DEV: Centralize user updates to a single MessageBus channel. (#17058) 
Introduces an interface to publish user updates on the server side and
helps to reduce the growing number of subscriptions on the client side.
 2022-06-13 14:27:43 +08:00
Andrei Prigorshnev 943cae82da FEATURE: propagate user status via message bus (#16944) 2022-05-30 13:41:53 +04:00
Andrei Prigorshnev 5c596273a0 FEATURE: user status (#16875) 2022-05-27 13:15:14 +04:00