Skip to content

Rename DF components #793

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

Merged
merged 6 commits into from
Jul 12, 2022
Merged

Rename DF components #793

merged 6 commits into from
Jul 12, 2022

Conversation

davidmrdavid
Copy link
Contributor

@davidmrdavid davidmrdavid commented Apr 7, 2022

Issue describing the changes in this PR

This PR contains some of the changes originally proposed in #746

This PR introduces two non-behavioral changes (i.e the end-user should not be affected in any way):

  • The Durable directory in the worker has been split into two folders: DurableSDK and DurableWorker. The former represents the SDK-specific components that, in the future, could be removed from this repo; this means it also represents the SDK-components that ought to exist in the external SDK. Meanwhile, the DurableWorker directory represents DF logic that is intrinsic to the worker, and ought to stay in this repo.
  • The new DurableSDK directory in particular is meant to be "drag and dropped" into an external SDK implementation; it's self-contained. As a result, we have removed any coupling of files within it with utility classes elsewhere in the repo. In practice, this means a few function definitions have been "duplicated" so that they now exist independently inside the "DurableSDK" directory. This is fine since we plan to eventually remove the DurableSDK repo from the worker.

In other words, I'm just slightly re-organizing the codebase to set the stage for the external SDK work. I decided to make this its own separate PR because a lot of files are affected and yet no functionality is changed, so I wanted to make sure this did not distract from the future PR where we actually change some behavior to enable the external DF SDK.

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
  • I have added all required tests (Unit tests, E2E tests)

Additional information

This needs to be backported to all DF-supported branches.

co-authored to an equal extent with @michaelpeng36

@davidmrdavid davidmrdavid marked this pull request as draft April 7, 2022 22:07
@davidmrdavid davidmrdavid marked this pull request as ready for review April 7, 2022 23:06
@davidmrdavid davidmrdavid changed the title [WIP] Rename DF components Rename DF components Apr 7, 2022
Copy link
Contributor

@AnatoliB AnatoliB left a comment

Choose a reason for hiding this comment

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

LGTM (just exclude profile.ps1 if not needed)

@davidmrdavid davidmrdavid merged commit 63e004e into dev Jul 12, 2022
@davidmrdavid davidmrdavid deleted the dajusto/rename-df-components branch July 12, 2022 19:58
davidmrdavid added a commit that referenced this pull request Sep 7, 2022
davidmrdavid added a commit that referenced this pull request Sep 7, 2022
davidmrdavid added a commit that referenced this pull request Sep 7, 2022
davidmrdavid added a commit that referenced this pull request Sep 7, 2022
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