Drop TimeoutSeconds and instead use the built-in Timeout from base FactAttribute #59
Comments
kzu
added a commit
that referenced
this issue
Oct 27, 2022
…ctAttribute Leave the (non-browsable) legacy property so that existing code continues to compile, but otherwise just expose the Timeout property as-is. We redeclare it so it's more accurate to the context of xunit.vsix in terms of what's measured. Fixes #59
kzu
added a commit
that referenced
this issue
Oct 27, 2022
…ctAttribute Leave the (non-browsable) legacy property so that existing code continues to compile, but otherwise just expose the Timeout property as-is. We redeclare it so it's more accurate to the context of xunit.vsix in terms of what's measured. Fixes #59
kzu
added a commit
that referenced
this issue
Oct 27, 2022
…ctAttribute Leave the (non-browsable) legacy property so that existing code continues to compile, but otherwise just expose the Timeout property as-is. We redeclare it so it's more accurate to the context of xunit.vsix in terms of what's measured. Fixes #59
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's confusing to have both.
The text was updated successfully, but these errors were encountered: