You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
I think we should plan a major overhaul of the processor/listener approach we currently use. It's too complicated and not of much use since we merged CASino and CASinoCore.
Plan
Find possible approaches to encapsulate the CAS logic
Architectural decision
Implement new architecture
???
Profit!
The text was updated successfully, but these errors were encountered:
The listeners encapsulate the same logic as the Rails Responder. The big plus by using Responder is the easy customizations of this behavior (user navigation, redirect and render) with a feature maintained in the rails core.
It would be far to easy to change the default behavior (from render to redirect) on some action without break any compatibility with the business logic (Processors).
As mentioned here:
Plan
The text was updated successfully, but these errors were encountered: