Summary: 46 instances, 45 unique

Text	Count
// TODO: we need to get rid of the (0) literal that indicates we	1
//  TODO: We always return null here.  Is there a pattern that allows us to change the method signature to "void" ?	1
//  TODO:  We directly instantiate this logger in two classes, creating	1
//TODO: Provide helper that generates useful attachment name from filed bug.	1
// TODO version, etc	1
# TODO:  Expand on this.	1
// TODO: https://github.com/Microsoft/sarif-sdk/issues/1425	1
// TODO: 'file' is another entry point type. should we be doing something here?	1
// TODO: Make the core baselining algorithm support BaselineFilteringMode.ToIncludedArtifacts	1
// TODO: Add additional logic to randomly select one or more required subsets and populate only those.	1
Message = new Message { Text = $"TODO: missing message construction for rule '{ruleId}'." }	1
// TODO tool message strings are not currently handled	1
// TODO we need better retrieval for locations than these defaults.	2
// TODO: need to accept this change soon	1
// TODO: why does this line of code provoke a stack overflow exception?	1
// TODO: Issue #932	1
// TODO: Ensure stackFrame.address and offset properties are being transformed correctly during v1 -> v2 conversion and vice-versa	1
// TODO: Make work item kind configurable for Azure DevOps filer	1
// TODO: Ensure stackFrame.address and offset properties are being transformed correctly during v1 -> v2 conversion and vice-versa	1
// TODO we should actually redact across the complete log file context	1
// TODO: Provide helper that generates useful attachment name from filed bug.	1
// TODO: Provide a meaningful representation of work item state in the model.	1
// TODO: add a warning to the list	1
// TODO: Region.ByteOffset is not being handled correctly in SemmleQlConverter. Fix this!	1
// TODO enable this change after current work	1
//  TODO: Add unit tests for remaining ShouldSerialize methods	1
throw new XmlException("XML Reader is in invalid state"); // TODO Code Analysis Exception	1
// TODO: Once we have migrated all the our messages to follow the convention,	1
// TODO: Have randomization logic to ensure a valid random index is generated during population.	1
//  TODO:  What's the point of having a bunch of static methods in an abstract class?	1
//  TODO Move this into a separate class for better unit testing	1
// TODO single-threaded write?	1
// TODO: FormatForVisualStudio doesn't handle	1
// TODO:  Removing this constructor broke the one of AbsoluteUriCommand entirely but all unit tests were passing	1
// TODO: Extend GitHub issue filer to add file attachments	1
new FirstDetectionTimeTestCase // TODO TEST CASE SHOWING CURRENT RUN WINS FOR NEW AND PREV RUN WINS FOR EXISTING	1
// TODO: Provide a useful SARIF-derived discussion entry	1
//  TODO:  Is it correct to modify options in a "validate" method?	1
//  TODO: This seems like uninformative error output.  All these errors get squished into one generic message	1
// TODO: make this async in the next iteration of the pipeline design	1
//  TODO: validate whether "actualOutputPath" can be created.	1
// TODO: Thoughtfully instrument this location and others	1
// TODO: root location pointer is "" in the log file. Didn't I already change that to "root" (=> "<root>"?)?	1
//  TODO: Verify a separate OutputFilePath works as expected	1
/// TODO:  Handle versioning of partial fingerprints.	1