Closed mgautierfr closed 2 years ago
Base: 96.88% // Head: 92.87% // Decreases project coverage by -4.00%
:warning:
Coverage data is based on head (
a649a61
) compared to base (66dac18
). Patch coverage: 58.33% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
BTW, I'm not sure of the best casing.
get_indexdata
, get_indexData
, get_index_data
?
get_wordcount
, get_word_count
, get_wordCount
, get_wordscount
?
BTW, I'm not sure of the best casing.
get_indexdata
,get_indexData
,get_index_data
?get_wordcount
,get_word_count
,get_wordCount
,get_wordscount
?
Ah I was wondering also what would be the most self-explanatory.
I'd suggest: get_indexdata
, get_wordcount
, get_geoposition
and so on but any of them makes sense so you should go with what you feel is more appropriate.
I'd suggest: get_indexdata, get_wordcount, get_geoposition and so on but any of them makes sense so you should go with what you feel is more appropriate.
It is what I've used. So we are good. I let you merge if you are ok with the PR
Code coverage has dropped significantly. A bit of automated testing might be welcome.
This pull request has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.
@mgautierfr Please finish this Pr.
Looks good but any exception in the IndexData methods ends up crashing the process. All the _cy_call_fct functions do enter the except block and set the trackeback in error[0] but for some reason it crashes instead of forwarding it up
This is more related to #42 than wrapping IndexData. I have a working version which need changes in python-libzim and libzim itself. I will create PRs soon.
As discussed, merging this despite the error handling issue and coverage.
Fixes #92