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

Change setup_incomplete? to setup_completed? in codebase #944

Closed
wants to merge 2 commits into from

Conversation

wende
Copy link
Contributor

@wende wende commented Feb 21, 2025

Relates to #937

@wende wende requested a review from mat-hek as a code owner February 21, 2025 14:21
@@ -69,7 +69,7 @@ defmodule Membrane.Core.Bin.State do
synchronization: nil,
initialized?: false,
terminating?: false,
setup_incomplete?: false,
setup_completed?: false,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why is incomplete: false a default value for a new structure?

Copy link
Member

@FelonEkonom FelonEkonom Feb 21, 2025

Choose a reason for hiding this comment

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

I guess it might be used as a flag indicating if action setup: :incomplete has been returned from handle_setup

Copy link
Member

@FelonEkonom FelonEkonom Feb 21, 2025

Choose a reason for hiding this comment

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

If I am wrong, then this flag would mean almost this same as :playback

Copy link
Member

Choose a reason for hiding this comment

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

Now I think that if I am right, maybe we could rename this flag to something less confusing (eg. setup_incomplete_returned??), but there is no sense in renaming it to setup_completed?

@wende wende closed this Feb 24, 2025
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