nimi-python
nimi-python copied to clipboard
Repeated capability tip in docstring should not depend on method's parameter metadata
Description of issue
Currently, Repeated capability tip is generated in docstring based on whether method contains channel-related parameters or presence of repeated_capability_type
in parameter metadata or 'channel_based': True
in attribute metadata.
Certain, fancy functions (e.g. get_site_pass_fail
) don't deal with the repeated capability directly, but rather call other methods that deal with it. In these cases, it's not accurate for the method metadata to include rep-cap based parameter, but including it is the only way to generate the rep cap tip in docstring. We need to figure out a solution to decouple these two things.