Add IProvideComponentHTMLView interface as partial to IComponent

[okjodom]

Enable query and access of IComponentHTMLView interface on IComponent.

Use Case

IComponentHTMLView avails remove() utility called by component hosts to trigger proper disposal of nested component views

[leeviana]

[anthony-murphy]

In general i don't think this is the right direction, as it makes using these interfaces more complicated. It would require a check for IComponentHTMLView and IComponentHTMLVisual to figure out if something can render.

This also isn't the long term plan for these interfaces, so i'd rather not make changes in the runtime until we have a better long term plan. You should work with @ChumpChief on the pattern you are using to get unblocked in the short term, and provide longer term feedback

[skylerjokiel]

I agree with Tony. The only way you would currently have an IComponentHTMLView is if you call addView on IComponentHTMLVisual. In that case you should have typing because you know the return type.

Our goal currently is to minimize (only have 1) render interface so developers don't need to do multiple checks to see how to render the object.

[leeviana]

I agree with Tony. The only way you would currently have an IComponentHTMLView is if you call addView on IComponentHTMLVisual. In that case you should have typing because you know the return type.

Our goal currently is to minimize (only have 1) render interface so developers don't need to do multiple checks to see how to render the object.

So then the question would be how can we call the remove() method that is only available via IComponentHTMLView right now?

[okjodom]

I agree with Tony. The only way you would currently have an IComponentHTMLView is if you call addView on IComponentHTMLVisual. In that case you should have typing because you know the return type.
Our goal currently is to minimize (only have 1) render interface so developers don't need to do multiple checks to see how to render the object.

So then the question would be how can we call the remove() method that is only available via IComponentHTMLView right now?

Assuming we call render and addView once for every IComponentHTMLVisual, we may keep a reference to resulting IComponentHTMLView.

From current usage, render is only called once (from visual) and calling remove from any referenced view logically results in cleanup of visual rather than view. What then makes views from addView unique? Would it be more intuitive to have render and remove on a single interface?

[okjodom]

@ChumpChief, @skylerjokiel Following up on this item, should we close PR and wait on interface redesign? Open an issue on the same?

[skylerjokiel]

@JoDoM , we should close this. Matt is working on a redesign of these interfaces and either way this is not the intended use case for this interface.

[ChumpChief]

Sorry, this fell off my radar over the holidays. Yes - we should close this.