New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session Config #5021
Session Config #5021
Conversation
Co-authored-by: Mostafa Khudair <59371810+mostafakhudair@users.noreply.github.com>
Publisher Class
Co-authored-by: MGatner <mgatner@icloud.com>
Co-authored-by: MGatner <mgatner@icloud.com>
Co-authored-by: MGatner <mgatner@icloud.com>
rename `application` to `app`
Co-authored-by: John Paul E. Balandan, CPA <51850998+paulbalandan@users.noreply.github.com>
…reign-key Fix bug with DB-Forge composite foreign keys
…onfig Add missing generators' config view file
c64e7c0
to
a6e1e6a
Compare
unfamiliar fail |
I've always wondered why this wasn't its own thing. Thanks for the work on this! I can't look in depth right now, but the failure is unrelated - I need to figure out how to make our architectural analysis installer version-independent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still pondering this. My hunch is we will need to adjust the priority for the Config files. More later.
a6e1e6a
to
8d8c82b
Compare
* | ||
* @var bool | ||
*/ | ||
protected $matchIP = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this removed? Is this duplicated by BaseHandler?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it is
|
||
============================== ============================================ ================================================= ============================================================================================ | ||
Preference Default Options Description | ||
============================== ============================================ ================================================= ============================================================================================ | ||
**sessionDriver** CodeIgniter\\Session\\Handlers\\FileHandler CodeIgniter\\Session\\Handlers\\FileHandler The session storage driver to use. | ||
**handler** CodeIgniter\\Session\\Handlers\\FileHandler CodeIgniter\\Session\\Handlers\\FileHandler The session storage driver to use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Table is malformed maybe due to spacing.
* | ||
* @var int | ||
*/ | ||
protected $lifetime = 7200; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think instead of replicating across all other handlers you can define this instead in BaseHandler. Even if there are handlers not using this, at least it is there available.
* | ||
* @var string | ||
*/ | ||
protected $handler = FileHandler::class; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would be in favor of marking these new props as private to reduce BC concerns in the future. This also promotes encapsulation. If a user will find this implementation as lacking, they can abstract one using the SessionInterface
instead of extending this and complaining this and that. But this is just my preference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand your preference.
But the way to extend the core classes is described in the user guide.
https://codeigniter4.github.io/CodeIgniter4/extending/core_classes.html#extending-core-classes
And CI users have been using it a lot for a long time.
Making properties as private is big change. I don't think it's easy to decide.
@mostafakhudair We would like to do another release soon, and I would love to see this as part of it. Could you address Paul's requests? I will make it a point to do my full review soon. |
It seems the base branch of this PR must be changed to |
@MGatner What is the version number of the next release? 4.1.5? 4.2.0? |
@MGatner It will be ready tomorrow |
* Set to `0` means expire when the browser is closed. | ||
======= | ||
* Setting to 0 (zero) means expire when the browser is closed. | ||
>>>>>>> 8d8c82bba537670571013bfdbd155c7a4e91b2aa |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a conflict.
@mostafakhudair Please redirect to @kenjis Next version will be 4.1.5, including everything that was on the 4.2 branch (minus |
@mostafakhudair Are we getting this back? Maybe in a fresh PR? Keen on this. |
Split session configuration from
Config::App
to a new config classConfig::Session
Checklist: