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

NewDefaultConfiguration() should return an error instead of calling panic() #70

Open
aogail opened this issue Sep 3, 2024 · 0 comments

Comments

@aogail
Copy link

aogail commented Sep 3, 2024

I am exploring using the Sailpoint Go SDK and discovered that sailpoint.NewDefaultConfiguration() panics if it can't find a configuration. I would prefer it to return an error instead of calling panic, so that higher level application logic can recognize the problem and report it appropriately to the user.

See

panic(fmt.Errorf("unable to find any config file"))

@aogail aogail changed the title NewDefaultConfiguration() should return an error instead of panicing NewDefaultConfiguration() should return an error instead of calling panic() Sep 3, 2024
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

1 participant