Meir Blachman
Meir Blachman
looks like this error is out of the scope of this project
@patrickweegen, Do you have an example of an Analyzers nuget package that can be installed using packet?
So basically if the global using file contains the testing library we should not perform the check on the namespace anymore. I think this should be implemented using some sort...
@bart-vmware part of the goals of this package is to encourage best practices when writing tests. so for the example: ```cs using XUnit.Fact as XFact; [XFact] public void SomeTest() {...
> A more efficient analyzer would register `AnalyzeSyntaxNode` with node type `ExpressionStatementSyntax`, instead of `RegisterCodeBlockAction`. Then there's no need to check for namespace imports, wherever they come from. Such an...
I think the fix here should be to not trigger the analyzer since asserting a constant value does not do anything
Now this is interesting 🤔
It's possible to debug a test and step into the analyzer's code. I'm not very familiar with the Visual Studio debug instance. I'll be happy to add it (pull request...
@SjaaLom is there autocomplete for the different definitions from faker? (name.firstName, name.lastName...) and if not, would it be possible to add that?
@mxschmitt is there a workaround for this? I was thinking of using something like ```js const cdp = await context.newCDPSession(page); let requestId; cdp.on('Network.requestWillBeSent', req => { requestId = req.requestId; });...