Steven Weerdenburg
Steven Weerdenburg
"What we support" is a fair point. Would we use a semver-major release for that?
Sorry, I think I'd been misremembering something I'd read. I'd meant changing by adding values in the future. I'd thought I read recommendation that adding values to a public enum...
Thanks @jnm2 It had been in a print copy of "Framework Design Guidelines". The other nuance I had forgotten about was that the switch/case/default concern would primarily be relevant when...
Hi @quldude Thanks for reporting this. What version were you upgrading from? Also, do you see the same on the newly released v3.13.3 version of the framework?
Hi @lnsandnkth welcome! I noticed you're interested in contributing a fix for this issue, would you like me to assign it to you? That'll help with coordination in the project...
Thanks for the report @IanKemp , do @manfred-brands 's work-arounds work for you? While not terribly clear from the titles, I suspect that this would be caught under the purview...
This may've been "fixed" in https://github.com/nunit/nunit/pull/4034 through the introduction of caching the attribute instances
Thanks for opening this 👍
Welcome @rnemeth90 ! Apologies for the late reply. It looks like this may've stalled out with a previous contributor. You are more than welcome to work on this.
I agree that swallowing exceptions is not ideal and I'm not a big fan of ignoring exceptions from attributes defined outside NUnit as it can be a common extension point...