EasyPost no method api_key #108
Comments
|
@embold-tyler hey, have you fixed it? |
|
sorry, I haven't had a chance yet. had a few things come up. |
|
@embold-tyler would you be up for fixing it? |
|
I have a branch I'm testing with a fix for this here: https://github.com/luna-lightblade/solidus_easypost/commits/easypost-5.0/ The core issue is breaking changes in the underlying easypost 5.0 gem which isn't version pinned as a dependency in this project. |
|
Hey @luna-lightblade We are in the process of fixing a lot of smaller issues around other extensions as well (we just made social_auth work) and are in the process to make solidus a little SEO friendlier. Is there anything you work on in particular apart of easypost and would you care about making a PR for the easypost extension as we did for social and starter frontend bugfixes? The community lives through contributors :) |
This was referenced Jan 5, 2025
JustShah
added a commit
to TriodecSolutions/solidus_easypost
that referenced
this issue
Feb 27, 2025
Enhances the security and maintainability of the SolidusEasypost API key handling and configuration. By removing the hardcoded API key assignment from the initializer, we significantly improve security. The API key management is now centralized within the Configuration class, which streamlines the process and makes it easier to maintain. Moreover, this change also fixes issue with the api_key for EasyPost mentioned in [Issues solidusio-contrib#108](solidusio-contrib#108). Additionally, this change allows for runtime updates to the API key without the need to modify the initializer, providing greater flexibility. To ensure consistency across tests, the SolidusEasypost configuration is now set up uniformly and uses factories effectively from the core gems, which helps maintain reliable and predictable test outcomes.
JustShah
added a commit
to TriodecSolutions/solidus_easypost
that referenced
this issue
Feb 27, 2025
Enhances the security and maintainability of the SolidusEasypost API key handling and configuration. By removing the hardcoded API key assignment from the initializer, we significantly improve security. The API key management is now centralized within the Configuration class, which streamlines the process and makes it easier to maintain. Moreover, this change also fixes issue with the api_key for EasyPost mentioned in [Issues solidusio-contrib#108](solidusio-contrib#108). Additionally, this change allows for runtime updates to the API key without the need to modify the initializer, providing greater flexibility. To ensure consistency across tests, the SolidusEasypost configuration is now set up uniformly and uses factories effectively from the core gems, which helps maintain reliable and predictable test outcomes.
JustShah
added a commit
to TriodecSolutions/solidus_easypost
that referenced
this issue
Feb 28, 2025
Enhances the security and maintainability of the SolidusEasypost API key handling and configuration. By removing the hardcoded API key assignment from the initializer, we significantly improve security. The API key management is now centralized within the Configuration class, which streamlines the process and makes it easier to maintain. Moreover, this change also fixes issue with the api_key for EasyPost mentioned in [Issues solidusio-contrib#108](solidusio-contrib#108). Additionally, this change allows for runtime updates to the API key without the need to modify the initializer, providing greater flexibility. To ensure consistency across tests, the SolidusEasypost configuration is now set up uniformly and uses factories effectively from the core gems, which helps maintain reliable and predictable test outcomes.
JustShah
added a commit
to TriodecSolutions/solidus_easypost
that referenced
this issue
Feb 28, 2025
Enhances the security and maintainability of the SolidusEasypost API key handling and configuration. By removing the hardcoded API key assignment from the initializer, we significantly improve security. The API key management is now centralized within the Configuration class, which streamlines the process and makes it easier to maintain. Moreover, this change also fixes issue with the api_key for EasyPost mentioned in [Issues solidusio-contrib#108](solidusio-contrib#108). Additionally, this change allows for runtime updates to the API key without the need to modify the initializer, providing greater flexibility. To ensure consistency across tests, the SolidusEasypost configuration is now set up uniformly and uses factories effectively from the core gems, which helps maintain reliable and predictable test outcomes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After updating the gem, a new error prevents the site from starting if the initializer has
EasyPost.api_key =and returnsundefined method 'api_key=' for EasyPost:Module (NoMethodError)EasyPost changed the way the client object is instantiated, so it no longer takes a global api_key but instead accepts the api_key when creating a new Client object per instructions here: https://github.com/EasyPost/easypost-ruby/blob/86b2575006f6fd3703b370cc00d72c3bb5b9d724/UPGRADE_GUIDE.md?plain=1#L28
The text was updated successfully, but these errors were encountered: