Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Share history in rooms in spaces by default #11446

Closed
wants to merge 1 commit into from

Conversation

gabrc52
Copy link
Contributor

@gabrc52 gabrc52 commented Aug 22, 2023

Signed-off-by: Gabriel Rodríguez rgabriel@mit.edu

Fixes element-hq/element-meta#377. Fixes element-hq/element-meta#1999. Both Element iOS and Element Android already do this by default (which seems to be inherited from the homeserver's behavior). Only Element Web has inconsistent behavior. This PR is opinionated in deliberately choosing the same behavior as on mobile.

Checklist

  • Tests written for new code (and old code if feasible) - N/A: change is very small
  • Linter and other CI checks pass
  • Sign-off given on the changes (see CONTRIBUTING.md)

Notes: history_visibility on rooms in spaces is now shared by default

element-web notes: New rooms created in spaces have their future history shared to all room members


Here's what your changelog entry will look like:

✨ Features

@gabrc52 gabrc52 requested a review from a team as a code owner August 22, 2023 06:24
@gabrc52 gabrc52 requested review from dbkr and richvdh August 22, 2023 06:24
@github-actions github-actions bot added the Z-Community-PR Issue is solved by a community member's PR label Aug 22, 2023
@richvdh richvdh added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Aug 22, 2023
@@ -233,7 +233,7 @@ export default async function createRoom(client: MatrixClient, opts: IOpts): Pro
createOpts.initial_state.push(makeSpaceParentEvent(opts.parentSpace, true));
if (!opts.historyVisibility) {
opts.historyVisibility =
createOpts.preset === Preset.PublicChat ? HistoryVisibility.WorldReadable : HistoryVisibility.Invited;
createOpts.preset === Preset.PublicChat ? HistoryVisibility.WorldReadable : HistoryVisibility.Shared;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setting aside for now whether this is a valid change (see element-hq/element-meta#377 (comment)):

If Element-Android and Element-iOS just follow the server's defaults in this situation, should we not also do so here?

@richvdh
Copy link
Member

richvdh commented May 17, 2024

@gabrc52 I'm assuming you're no longer interested in working on this, so am closing it accordingly. We can reopen if you're still interested in it.

@richvdh richvdh closed this May 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements Z-Community-PR Issue is solved by a community member's PR
Projects
None yet
2 participants