Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: personal spaces can be made private without a pro plan #776

Merged

Conversation

BlankParticle
Copy link
Member

@BlankParticle BlankParticle commented Sep 11, 2024

What does this PR do?

Fixes ENG-140
Personal spaces can always be made private regardless of pro plan
Once affected spaces are private again, we don't allow to open them to avoid confusion

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist

Required

  • Read Contributing Guide
  • Self-reviewed my own code
  • Tested my code in a local environment
  • Commented on my code in hard-to-understand areas
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the UnInbox Docs if changes were necessary

Copy link
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BlankParticle and the rest of your teammates on Graphite Graphite

@BlankParticle BlankParticle marked this pull request as ready for review September 11, 2024 10:51
@McPizza0
Copy link
Member

@BlankParticle i think we should change this to never allow personal spaces to be public in the first place
will be less confusing for people

@BlankParticle
Copy link
Member Author

@BlankParticle i think we should change this to never allow personal spaces to be public in the first place will be less confusing for people

there might be use cases for people to have open personal spaces, also we need to alllow people who have accidently made their spaces open

@McPizza0
Copy link
Member

there might be use cases for people to have open personal spaces, also we need to alllow people who have accidently made their spaces open

maybe only a tiny few usecases
most of the time they can just add people to the space
If someone accidentally made it open; we can account for that.

if personal space is true, allow it to be set to private, but dont allow to be set to open (open is disabled)

@BlankParticle
Copy link
Member Author

ok, will do that

@BlankParticle BlankParticle force-pushed the blank/fix/allow-making-personal-space-private-always branch 2 times, most recently from 6da7062 to 28de097 Compare September 11, 2024 11:12
@BlankParticle
Copy link
Member Author

BlankParticle commented Sep 11, 2024

@McPizza0, have done as you asked, also added the missing backend checks

@BlankParticle BlankParticle force-pushed the blank/fix/allow-making-personal-space-private-always branch from 28de097 to 9b56a6b Compare September 11, 2024 11:50
Copy link
Member Author

BlankParticle commented Sep 11, 2024

Merge activity

@BlankParticle BlankParticle force-pushed the blank/fix/allow-making-personal-space-private-always branch from 9b56a6b to e33c521 Compare September 11, 2024 12:00
@BlankParticle BlankParticle merged commit 05e599a into main Sep 11, 2024
4 checks passed
@BlankParticle BlankParticle deleted the blank/fix/allow-making-personal-space-private-always branch September 11, 2024 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants