Skip to content
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

About log.Fatal() #9

Open
habuka036 opened this issue Jul 27, 2020 · 3 comments
Open

About log.Fatal() #9

habuka036 opened this issue Jul 27, 2020 · 3 comments

Comments

@habuka036
Copy link
Contributor

Hi there,

This library uses log.Fatal() in some codes despite that causes exit the program when failed to connect for OANDA API.

So, I want to suggest the error return to the caller instead of use log.Fatal().

Of cause, my suggestion has a big impact on the Interfaces of this library. Therefore I hope someone will come up with a good idea more than my suggestion.

Thank you for this great library,

Osamu

@stewi1014
Copy link
Contributor

I originally forked this project for this reason, and intended on creating a PR with changes to error handling, but I ended up making far more changes than I anticipated and so didn't make the PR. I don't think I'm going to maintain my fork any more as I'm no longer using it but I'd be happy to revert my more extreme changes and see what you think about maybe merging it @AwolDes

@AwolDes
Copy link
Owner

AwolDes commented Aug 10, 2020

@stewi1014 more than happy for you to put up a PR with any changes you've made. I haven't worked on this for awhile, but I'm glad people are finding it useful and forking the project 💯

@stewi1014
Copy link
Contributor

I cleaned up the git history and created #10 that should address this along with some other changes I made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants