-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Create Config::Cookie Class #4508
Create Config::Cookie Class #4508
Conversation
926ac46
to
105302e
Compare
This is a good change. I would like to make a release this weekend, which would solidify all the Cookie changes since 4.1 - let's be sure to get this finished so it can be included. |
@MGatner I think next release should be done without any of new Cookie Class, because of cookie class is bloated with alot usless methods and need to be refactored, also to avoid BC |
@mostafakhudair I thought there had been significant improvements to our Cookie handling since the last release, work that you and @paulbalandan both did. What do you think should be held back? Is it something that can easily be reverted and re-applied for the following release? Paul, what are your thoughts? |
6d90b06
to
42bdb15
Compare
Bloated? What aspects of the If you can pinpoint the places that needs refactor, we'd consider excluding cookie in the release and perhaps I'd do the refactor myself. Otherwise, aside from the config reassignment, the cookie class is stable as-is. |
42bdb15
to
ad5f42a
Compare
@mostafakhudair please incorporate @paulbalandan review |
21ab076
to
216b095
Compare
82a4907
to
6f17f45
Compare
6f17f45
to
91c8c73
Compare
What is wrong with tests? |
That seems race condition issue in SQLSRV action. It seems unrelated. |
Have tests been rerun since #4539? |
Yes, twice |
Thank you, @mostafakhudair |
🥳 |
While we are taking a step forward to make config folder separated as much as possible, Cookie class should have it's own config file