A suite of tools for Community Data Analysis

Forked from Kevin Ottens / ComDaAn

  • Christelle Zouein's avatar
    Mapping rulesets to the corresponding repository · 31a10566
    Christelle Zouein authored
    Rulesets are now stored in a dictionary (key : path to repository, value :
    list of modules found ascendingly from repo).
    is_entry_acceptable and postprocess_entry are only applied on rulesets
    relevant to the repository in question.
    
    Mapping rulesets to the corresponding repo
    
    Actually mapping rulesets to the corresponding repository instead of to the
    directory in which they were found.
    In the posrprocess and is_entry_acceptable functions, looping on dict
    keys turned into a simple lookup.
    
    Lookup for rulesets moved one function call above
    
    Lookup for rulesets moved to the function call above postprocessing and
    is_entry_acceptable as well as some other adjustments (abs_path used as
    a key instead of repo name for dictionary, function renaming -> plural
    form and more efficient get statement replaced if)
    
    mod variable name changed to ruleset
    
    Returning false when entry isn't acceptable
    
    Added if statement in the for loop to return false when the entry isn't
    acceptable instead of wrongly just calling is_entry_acceptable.
    31a10566
Name
Last commit
Last update
rulesets Loading commit data...
.gitignore Loading commit data...
LICENSE Loading commit data...
Pipfile Loading commit data...
Pipfile.lock Loading commit data...
README.md Loading commit data...
activity.py Loading commit data...
centrality.py Loading commit data...
gitparsing.py Loading commit data...
network.py Loading commit data...
pyproject.toml Loading commit data...
setup.cfg Loading commit data...
teamsize.py Loading commit data...