[Suggestion] HtmlResult/AssetManager.GetLayoutHtml+ abstraction

[rayph]

I have been following IdSrv with great interest for a while now and the new v3 architecture is looking really good for a 1st preview.

My suggestion expands on #164 but would enable a deeper customisation, rather than only making the existing html/assets customisable I'd like to see the currently static AssetManager abstracted out so completely bespoke view/model rendering can be injected. This would enable folks to plug in their own presentation layer+asset management while still getting the benefit of all the logic and protocol handling in core.

From what I can see it should be quite straightfoward to pull an interface out for AssetManager and have the desired or default implementation added to the container via a PluginConfiguration property. All members of AssetManager could be more loosely coupled and customisable.

Forgive me if this is already being planned, or if not what do you think of this as a feature?

[brockallen]

Thanks for the suggestion. We'll see what we can do. Thanks.

[brockallen]

Ok, this was added. I'd love feedback if/when you have time. Thx.

[rayph]

Looks great! Just had a look at the latest code and I like the approach. It even looks possible to augment the view models to enrich the views beyond the vanilla feature set. Wonderful stuff.

Which makes me wonder; what sorts of things will appear in the environment dictionary? I'm hoping for something about the relying party / request origin to be available to the view service :)

I'll experiment with plugging in a different view engine pretty soon and will let you know how the implementation feels.

Thanks for getting this onto the backlog and into code this quickly!

[brockallen]

The env dictionary is the owin environment in case something from the request was needed.