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

Move internal usages of IFluidObject to provider pattern #8076

Closed
Tracked by #7613
anthony-murphy opened this issue Nov 1, 2021 · 0 comments · Fixed by #8354
Closed
Tracked by #7613

Move internal usages of IFluidObject to provider pattern #8076

anthony-murphy opened this issue Nov 1, 2021 · 0 comments · Fixed by #8354
Assignees
Milestone

Comments

@anthony-murphy
Copy link
Contributor

anthony-murphy commented Nov 1, 2021

No description provided.

@ghost ghost added the triage label Nov 1, 2021
@anthony-murphy anthony-murphy self-assigned this Nov 1, 2021
@anthony-murphy anthony-murphy added this to the November 2021 milestone Nov 1, 2021
@ghost ghost removed the triage label Nov 1, 2021
anthony-murphy added a commit that referenced this issue Nov 15, 2021
anthony-murphy added a commit that referenced this issue Nov 16, 2021
anthony-murphy added a commit that referenced this issue Nov 17, 2021
This change moves our leaf level example packages off of IFluidObject and to FluidObject

related to #8076
anthony-murphy added a commit that referenced this issue Nov 17, 2021
FluidObject and IFluidObject are intentionally compatible. This change adds FluidObject to the type signature of our scope and fluid export properties, to ease the transition. I've also updated our internal usages to use scope and fluid export via FluidObject.

related to #8076
anthony-murphy added a commit that referenced this issue Nov 19, 2021
…ases (#8354)

Adds a note to breaking about the deprecation of IFluidObject and updates remaining internal usages which are not synthesize which will come with #8074

fixes #8076
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant