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
I ran into this issue while building a feature for Learn.co. I needed to create a new Namecheap account, and then register a domain under that account, something which required having these two parameter have different values.
The global parameters (required) for "ApiUsername" and "Username" are hardcoded in the gem, so I had to manually use Faraday to make the requests.
I think the solution would be a conditional check for the "Username" global parameter coming from the client before assigning in the API configuration of the gem. I will take a stab at this.
The text was updated successfully, but these errors were encountered:
I ran into this issue while building a feature for Learn.co. I needed to
create a new Namecheap account, and then register a domain under that
account, something which required having these two parameter have different
values.
The global parameters (required) for "ApiUsername" and "Username" are
hardcoded in the gem, so I had to manually use Faraday to make the requests.
I think the solution would be a conditional check for the "Username"
global parameter coming from the client before assigning in the API
configuration of the gem. I will take a stab at this.
I Follow The Code of Awesomeness:
I dare to dream big
I evolve through learning
I am positive & passionate
I practice transparency & candor
I help others rock their greatest lives
I turn customers into raving fans
I am grateful & I celebrate life
I kick serious ass
I am a money magnet
I honor my words with action
I ran into this issue while building a feature for Learn.co. I needed to create a new Namecheap account, and then register a domain under that account, something which required having these two parameter have different values.
The global parameters (required) for "ApiUsername" and "Username" are hardcoded in the gem, so I had to manually use Faraday to make the requests.
I think the solution would be a conditional check for the "Username" global parameter coming from the client before assigning in the API configuration of the gem. I will take a stab at this.
The text was updated successfully, but these errors were encountered: