-
-
Notifications
You must be signed in to change notification settings - Fork 616
MatrixRTC: Rename MembershipConfig
parameters
#4714
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
base: develop
Are you sure you want to change the base?
Conversation
MembershipConfig
parametersMembershipConfig
parameters
Do we want to make this backwards compatible and introduce a couple of deprecated old properties? |
db55170
to
c569893
Compare
Can we make sonar cloud happy event though we use the deprecated fields as fallback? |
We do already have the state `hasMemberEvent` that allows to distinguish the two cases. No need to create two dedicated actions.
- deprecate isJoined (replaced by isActivated) - move Interface types to types.ts
5acd034
to
052cef9
Compare
fc35b3c
to
3d60f53
Compare
I am wondering if this should get a breaking change label because of the one property robin mentioned got removed. Technically it does not change anything however since it will continue to be a property with no effect but one can keep it in the config file. Does it make more sense to add the breaking change label to the version that then removes the deprecated fields? |
T-Deprecation seems appropriate to me |
Checklist
public
/exported
symbols have accurate TSDoc documentation.