-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
unify managed_component and simple_component #1421
Comments
This could also solve #548. |
sithhell
added a commit
that referenced
this issue
Oct 28, 2015
To move forward with #1421 and to get users to already use the new API, those two classes have been added. They just forward to their respective simple component facilities. The examples and performance counters have been adapted to not expose either managed or simple component anymore.
sithhell
added a commit
that referenced
this issue
Oct 28, 2015
To move forward with #1421 and to get users to already use the new API, those two classes have been added. They just forward to their respective simple component facilities. The examples and performance counters have been adapted to not expose either managed or simple component anymore.
Closed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed. Please re-open if necessary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently have both,
managed_component
andsimple_component
. From a user perspective, it is, at first sight unclear when to use what. In addition, migratingmanaged_component
seems to be overly complex.The consensus would be to remove
managed_component
entirely which will result in a simpler component user API.The text was updated successfully, but these errors were encountered: