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.

Sign up for GitHub

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

Jump to bottom

Remove git code from protocol-definitions #9003

Closed
Tracked by #4683
scarlettjlee opened this issue Feb 3, 2022 · 1 comment
Closed
Tracked by #4683

Remove git code from protocol-definitions #9003

scarlettjlee opened this issue Feb 3, 2022 · 1 comment
Labels
ado Issue is tracked in the internal Azure DevOps backlog good first issue Good for newcomers status: stale triage

Comments

@scarlettjlee
Copy link
Contributor

scarlettjlee commented Feb 3, 2022 •
edited
Loading

Deprecate and remove GIT specifics from protocol-definitions. Anything still needed should be moved to r11 driver(s).

  • FileMode
  • ITreeEntry.mode (only File and Directory seem to be used in client, so using ITreeEntry.type instead is sufficient to map)

This is marked "good first issue" for learning repo structure of separately versioned packages and deprecating APIs. It's not a trivial change.
@ghost ghost added the triage label Feb 3, 2022
This was referenced Feb 3, 2022
Open
Closed
@scarlettjlee scarlettjlee added the good first issue Good for newcomers label Mar 1, 2022
@curtisman curtisman added the ado Issue is tracked in the internal Azure DevOps backlog label Jun 20, 2022
@ghost ghost added the status: stale label Dec 18, 2022
@ghost
Copy link

ghost commented Dec 18, 2022

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!

@ghost ghost closed this as completed Dec 26, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ado Issue is tracked in the internal Azure DevOps backlog good first issue Good for newcomers status: stale triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@curtisman @scarlettjlee