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
When using the MaxMind driver in your package, I've encountered an issue where the timezone field becomes null during the processing of the IP. This problem specifically occurs in the hydrate method of the driver when transferring information from the Fluent object to the Position object.
The underscore in the property name seems to be the root cause, as the actual property on the Fluent class is named timezone without the underscore. To address this issue in my application, I implemented a temporary workaround by overriding the driver's hydrate method as follows:
I believe a fix for this issue could involve updating the driver and related tests, and I can put up a pull request if this approach aligns with the project's goals. Please let me know if you have any thoughts or feedback on this proposed solution.
Thank you for your time and consideration.
The text was updated successfully, but these errors were encountered:
When using the MaxMind driver in your package, I've encountered an issue where the timezone field becomes null during the processing of the IP. This problem specifically occurs in the hydrate method of the driver when transferring information from the Fluent object to the Position object.
The underscore in the property name seems to be the root cause, as the actual property on the Fluent class is named
timezone
without the underscore. To address this issue in my application, I implemented a temporary workaround by overriding the driver's hydrate method as follows:I believe a fix for this issue could involve updating the driver and related tests, and I can put up a pull request if this approach aligns with the project's goals. Please let me know if you have any thoughts or feedback on this proposed solution.
Thank you for your time and consideration.
The text was updated successfully, but these errors were encountered: