Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / parasquid/namecheap issues and pull requests
#15 - Created a mechanism for forcing sandbox use
Pull Request -
State: open - Opened by dtynan about 3 years ago
#14 - Unable to use two users (APIUsername & Username)
Issue -
State: open - Opened by skipsuva over 8 years ago
- 1 comment
#13 - Links to Namecheap API documentation is Out of Date
Issue -
State: open - Opened by skipsuva over 8 years ago
#12 - Add support for users.address API call
Issue -
State: open - Opened by clarkewd over 9 years ago
- 2 comments
#11 - Use of client_ip is not thread safe
Issue -
State: open - Opened by kyledrake almost 10 years ago
- 2 comments
#10 - Supports explicit endpoint configuration
Pull Request -
State: open - Opened by jkassemi over 10 years ago
- 3 comments
#9 - Gem compatibility with Rails
Pull Request -
State: closed - Opened by phillipp almost 11 years ago
- 6 comments
#8 - namecheap gem crashes Rails
Issue -
State: closed - Opened by phillipp almost 11 years ago
- 3 comments
#7 - Add explicit requires and remove load path
Pull Request -
State: closed - Opened by phillipp almost 11 years ago
#6 - Add travis to run specs
Issue -
State: closed - Opened by dmyers over 11 years ago
#5 - Merge back forked repos
Issue -
State: open - Opened by parasquid over 11 years ago
- 1 comment
#4 - Use VCR / WebMock for testing Namecheap replies
Issue -
State: open - Opened by parasquid over 11 years ago
- 2 comments
#3 - Switch license from GPLv3 to LGPLv3
Issue -
State: closed - Opened by parasquid over 11 years ago
#2 - Replace custom gem configuration code with https://github.com/krautcomputing/gem_config
Issue -
State: open - Opened by parasquid over 11 years ago
#1 - Added more client apis
Pull Request -
State: closed - Opened by dmyers over 11 years ago
- 5 comments