This pull request solves #10 therefore adding support for route groups.
Additions
The GeoGroup class: This class is responsible of defining the route group and applying the geo-constraint on it.
The geomacro method: This is a Router macro method used to define the GeoGroup.
The ControlsAccess trait: Resolves duplicate code, contains the access methods (allow, deny, allowFrom and denyFrom).
The HasCallback trait: Resolves duplicate code, contains the callback-related methods (loadProxies, setCallback and the default callbacks)
Potential Changes
I am concerned about the ControlsAccess and HasCallback traits defining the callback, proxies, strategy and countries properties, i think this might have to be changed to calling methods such as getCallbackProperty as seen in many Laravel traits, so would you please share your opinion concerning this topic?
This pull request solves #10 therefore adding support for route groups.
Additions
GeoGroupclass: This class is responsible of defining the route group and applying thegeo-constrainton it.geomacro method: This is a Router macro method used to define theGeoGroup.ControlsAccesstrait: Resolves duplicate code, contains the access methods (allow,deny,allowFromanddenyFrom).HasCallbacktrait: Resolves duplicate code, contains the callback-related methods (loadProxies,setCallbackand the default callbacks)Potential Changes
I am concerned about the
ControlsAccessandHasCallbacktraits defining thecallback,proxies,strategyandcountriesproperties, i think this might have to be changed to calling methods such asgetCallbackPropertyas seen in many Laravel traits, so would you please share your opinion concerning this topic?