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

Config option to disable abbreviations #122

Closed
VolkerSiep opened this issue Jul 11, 2018 · 1 comment · Fixed by #208
Closed

Config option to disable abbreviations #122

VolkerSiep opened this issue Jul 11, 2018 · 1 comment · Fixed by #208
Milestone

Comments

@VolkerSiep
Copy link

Hi,

in reference to the linked line of code (datatree.py#L307):

I find these abbreviations for my case (using standard lib unittest) disadvantageous and hacked it into
return self.testresults[row].name without much understanding the code :). Let me suggest to add a configuration option to the "Configure tests" dialog that allows to switch the feature on and off.

BTW: Thanks for the plugin. Good work!

With best regards / Volker

@jitseniesen
Copy link
Member

Yes, it does depend on naming and other conventions whether these abbreviations are advantaguous, so it's a good suggestion to add a config option for this.

Thanks for your kind words.

@jitseniesen jitseniesen self-assigned this Jul 16, 2018
@jitseniesen jitseniesen added this to the v0.4 milestone Jul 16, 2018
@jitseniesen jitseniesen modified the milestones: v0.4, v0.5 Dec 28, 2019
@goanpeca goanpeca removed this from the v0.5 milestone Feb 23, 2020
@jitseniesen jitseniesen added this to the v0.5.1 milestone Jan 6, 2022
@jitseniesen jitseniesen removed the v0.5.0 label Jan 6, 2022
@jitseniesen jitseniesen modified the milestones: v0.5.1, v0.5.2 Aug 17, 2022
@jitseniesen jitseniesen removed their assignment Aug 17, 2022
@jitseniesen jitseniesen modified the milestones: v0.5.2, v0.6.0 Mar 24, 2023
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

Successfully merging a pull request may close this issue.

3 participants