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

Add breaking.md #9701

Merged
merged 1 commit into from
Mar 31, 2022
Merged

Add breaking.md #9701

merged 1 commit into from
Mar 31, 2022

Conversation

jatgarg
Copy link
Contributor

@jatgarg jatgarg commented Mar 31, 2022

Add in upcoming changes about IDirectory extending IDisposable.

@jatgarg jatgarg requested a review from heliocliu March 31, 2022 18:49
@jatgarg jatgarg requested a review from a team as a code owner March 31, 2022 18:49
@jatgarg jatgarg self-assigned this Mar 31, 2022
@github-actions github-actions bot added breaking change This PR or issue would introduce a breaking change base: main PRs targeted against main branch labels Mar 31, 2022

### Doing operations not allowed on deleted sub directory
Users will not be allowed to do operations on a deleted directory. Users can subscribe to `disposed` event to know if a sub directory is deleted. Accessing deleted sub directory will throw `UsageError` exception now.

### IDirectory extends IDisposable
IDirectory has started extending IDisposable. This means that users implementing the IDirectory interface needs to implement IDisposable too now.
Copy link
Contributor

Choose a reason for hiding this comment

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

just to confirm, is the plan to change the implements Partial<IDisposable> to implements IDisposable in the future?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes.

@jatgarg jatgarg merged commit 85fc974 into microsoft:main Mar 31, 2022
@jatgarg jatgarg deleted the test2 branch March 31, 2022 19:30
@@ -18,10 +18,14 @@ There are a few steps you can take to write a good change note and avoid needing

## 0.58 Upcoming changes
Copy link
Member

Choose a reason for hiding this comment

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

@heliocliu I would recommend changing this to not say 0.58, maybe "Upcoming changes (ETA 0.59)" or something. Or just "Upcoming changes" and as part of the release clear the section out every time...?

Copy link
Contributor

Choose a reason for hiding this comment

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

I definitely wanted to avoid the step of needing to clear them out, but it's true that having a version associated with the upcoming change has been confusing for people :/ But yeah the ease of understanding probably outweighs needing to delete stuff occasionally there.

Copy link
Contributor

Choose a reason for hiding this comment

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

Why would you need to clear them out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
base: main PRs targeted against main branch breaking change This PR or issue would introduce a breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants