Lynicon now can be adapted to work seamlessly with SPA applications, sourcing content data through the SPA's router to be integrated with what it displays, and showing you the content editor for the current url alongside a preview of the SPA in the appropriate state for that url.
This is achieved on the server side by configuration of routes to use the SpaDiversionStrategy instead of the EditorDiversionStrategy. What this does is to adapt the routing options of a content managed route to work with a SPA fallthrough route so that requests for HTML pages fall through to be handled by this route. Requests when logged in by an editor still are diverted to show an editor, and requests for JSON still return JSON content.
Usually you will want to switch out EditorDiversionStrategy for SpaDiversionStrategy in all content routes. This is done by the LyniconSystemBuilder.SetDiverter method as below in the ConfigureServices method in Startup.cs:
services.AddLynicon(...) .SetDiverter(new SpaDataDiverter());