-
Notifications
You must be signed in to change notification settings - Fork 3
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
Contributing to this Repo: remove panic and unwrap #5
Comments
Hi @Bas-Man. I agree, there are a lot of areas this could be improved. I really hacked it together quickly while initially learning Rust. Your help is much appreciated. Removing the panics and unwraps would be great. I incorrectly closed the pull request about making The second pull request is also a good one. Ideally |
Yes. Ideally parse_dir would only parse valid files. The [should_panic] is a temp fix to get all tests passing including the panic. I am already thinking about how to resolve the parse_dir so that it does not actually panic. But moving step by step to avoid conflicts. I also would like to make most of the struct data private with accessors. But that might be over engineering. |
@bbustin could you point to a good source of demarc samples. |
I do not know a good source of samples, unfortunately. I was just using ones I was receiving on my mail server from Google, Yahoo, and other places. |
No worries. I will work with what we have. I would like to remove the guard in parse_dir() The |
👍 |
Hi,
I am interested in contributing to this repo. I was thinking of writing my own. But this seems to be a great place to start and contribute.
Some of the issues that I see in the code that I think I can help with.
panic
hard coded. I would like to remove this and make the function return aresult
unwrap
s that might fail on a malformed xml file.directory
as aPath
in a nice way.I have already raised two PRs to address some very simple things.
test_parse_dir
by adding the#[should_panic]
See pr Add test to expect panic #3parse_reader
private as this does not need to be public in the current code.The text was updated successfully, but these errors were encountered: