You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The deprecated API is the add method on IntervalCollection, called when adding a new interval to a given collection. The type parameter is being removed from this API.
Context
The type parameter of this API is being removed to prevent callers of add from specifying an IntervalType. The default type is IntervalType.SlideOnRemove, and all intervals will now be created with that type.
Approach
Simply call IntervalCollection.add without the interval type parameter, so a maximum of 4 parameters will be passed in.
Dependencies
None.
Compatibility Concerns
None.
Phases
Check in overloaded add method for the original signature as well as the updated signature.
Ensure that all partners calling this method do not pass in an interval type.
Remove the 5-parameter signature, and leave only the add implementation without the type parameter.
Expected Timeline
The API will likely be removed in the 2.0.0-internal.9.0.0 release (in 2 major releases).
Open Questions
None.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has had no activity for 180 days. It will be closed if no further activity occurs within 8 days of this comment. Thank you for your contributions to Fluid Framework!
Deprecated API
The deprecated API is the add method on IntervalCollection, called when adding a new interval to a given collection. The type parameter is being removed from this API.
Context
The type parameter of this API is being removed to prevent callers of add from specifying an IntervalType. The default type is IntervalType.SlideOnRemove, and all intervals will now be created with that type.
Approach
Simply call IntervalCollection.add without the interval type parameter, so a maximum of 4 parameters will be passed in.
Dependencies
None.
Compatibility Concerns
None.
Phases
Expected Timeline
The API will likely be removed in the 2.0.0-internal.9.0.0 release (in 2 major releases).
Open Questions
None.
The text was updated successfully, but these errors were encountered: