Justin Buchanan

Shared shproj code formatting

Currently when viewing code in shared projects (shproj, projitems) all the JustCode -> Code options are disabled, and keyboard shortcuts don't work. Files in shared projects need to be handled as normal, please!
Feature Request by Justin Buchanan Status: New Comments: 0 Last update: 2014-09-18T22:06:19 by Justin Buchanan
0
Eric Boumendil

Nested ObsoleteAttributes

If an obsolete method invokes an other obsolete method, no warning should be generated by JustCode for the inner obsolete call (just like VS compiler do).
Problem by Eric Boumendil Status: New Comments: 0 Last update: 2014-09-17T08:28:42 by Eric Boumendil
0
Metro Sauper

Eplicit test cases are not skipped.

JustCode test runner does not seem to skip NUnit test cases and classes attributed as Explicit.
Problem by Metro Sauper Status: New Comments: 0 Last update: 2014-09-15T21:44:42 by Metro Sauper
0
Nikolay Valchev

justcode.json file for settings

I think it would greatly benefit JustCode if many of its settings could be optionally declared in a very simple *.JSON file within a solution, or even on a project basis (though I imagine the project basis is more complicated, so solution seems the first go-to)

A file would not need to be very complicated. The initial idea is to work sort of like a "web.config" file in ASP.NET, where the system settings are the global defaults, and then there can be more specific ones for the user, and then at last the solution might have a more explicit one ("justcode.json") to declare anything unique.

This would have the advantage of being source control shared, which is a big plus on teams or for people who work between multiple locations.

In my initial proposal, I am mostly looking at showing ways to handle things that should be excluded from JustCode, or things that need to be slightly related, for example, right now if you want to convince JustCode not to analyze certain parts of your file, you have two options;

1. exclude the specific language(s) from analysis
2. write a 'filter' in that small little text box and hope it matches the pattern, and exclude it there.

Both of these do work, but that makes it something that is system-wide by default. It isn't something you might desire all the time, and it is kind of hard to manage. Something I propose is a simpler declaration, like this, in a .json file.

{
exclude: [
"*.min.js", // exclude minified javascript
"*/_content/**", // exclude all files under a _content folder.
"*/bootstrap/*.less", // exclude all .less files under the /bootstrap folder
"{:External.Resources}", // exclude all files in project called 'External.Resources"
]
}

This could be taken a step further by allowing the user to declare even explicit errors to ignore.

{
exclude: [
"*.min.js", // exclude minified javascript
"*/_content/**", // exclude all files under a _content folder.
"*/bootstrap/*.less", // exclude all .less files under the /bootstrap folder
"{:External.Resources}", // exclude all files in project called 'External.Resources"
],
ignore: [
{
pattern: "*.min.js",
errors: [
"Unexpected \"",
"Unexpected end of line"
]
}
]
}

Now, in a very clean, succinct, and much easier to manage place, we've declared very specific settings that will let us customize and optimize JustCode's ability to not analyze select files. This is useful for situations where you are using a third party library that works fine, but doesn't quite fit JustCode's standards (for example, I cite the "bootstrap" library. If you load up all of it's .LESS files, JustCode throws a ton of errors - but the truth is that the whole thing compiles just fine. This is also true of Telerik's own Kendo UI's .LESS files)

To add to that, this .json file could easily be expanded with new features as they are implemented. I cite an example that I used in another project that used .json files for its config, to make .LESS compiling smarter...

{
exclude: [
"*.min.js", // exclude minified javascript
"*/_content/**", // exclude all files under a _content folder.
"*/bootstrap/*.less", // exclude all .less files under the /bootstrap folder
"{:External.Resources}", // exclude all files in project called 'External.Resources"
],
behaviors: [
{
language: "LESS",
extension: "*.less",
root: [
"*/kendo/web/kendo.common.less",
"*/kendo/web/kendo.bootstrap.less",
"*/kendo/web/theme-template.less"
],
incomplete: [
"*/kendo/web/common/*", // all of the kendo sub-files
"*/kendo/common/*" // the typical transitions.less file
]
}
]
}

This is obviously an extremely specific use-case, but I am very certain that many developers encounter this sort of thing frequently, and the current options JustCode gives for modifying behavior are (A) machine wide and (B) very hard to work with and tune (trying to manage filters in that tiny little text box is just frustrating. It is like trying to handle a massive function in Excel)
Feature Request by Nikolay Valchev Status: New Comments: 0 Last update: 2014-09-03T08:11:11 by Nikolay Valchev
0
Eric Boumendil

Warn if throwing a NotImplementedException

I often add a // TODO comment inside methods to implement.

If a warning was generated, I wouldn't do it.

To me, it is not a production code (thus, a warning is applicable) because if I do not want to implement a method, I use then NotSupportedException in place of NotImplementedException.
Feature Request by Eric Boumendil Status: New Comments: 0 Last update: 2014-09-02T13:49:23 by Eric Boumendil
0
John Dziurlaj

Supress Code Analysis Warnings for Generated Code

Generated code usually cannot be easily changed to conform to style guidelines set by JustCode Code Analysis. Thus code with the block below should not participate in Code Analysis Warning Generation.

//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
// Runtime Version:4.0.30319.18408
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------
Idea by John Dziurlaj Status: New Comments: 0 Last update: 2014-08-28T14:43:29 by John Dziurlaj
0
Stuart Hemming

Pause analysis during compile

It would be nice if there were an option to pause anaysis until a build is completed.
Feature Request by Stuart Hemming Status: Reviewed Comments: 1 Last update: 2014-08-15T13:44:16 by Patrick Gendron
0
Eric Boumendil

Warning rule for "async void" method signature

It is widely recognized that we should almost never write a method signature like "async void MethodName()". The single exception I know to this rule is event handlers.
It would be nice if JustCode could take care of this.
Idea by Eric Boumendil Status: New Comments: 0 Last update: 2014-08-08T12:47:53 by Eric Boumendil
0
Brandon Campea

JustCode thinks string.Format() has unused variables when using a const for input

In C#, using string.Format() with a const string as the input for composite formatting will cause JustCode to grey-out the rest of the input parameters as 'unused arguments'. It does not seem to be able to "see inside" the const string to determine how many formatting anchors are present to check that the parameter count matches.

Please see the attached screenshots for examples.
Problem by Brandon Campea Status: New Comments: 1 Attachments: 2 Last update: 2014-08-07T15:44:04 by Vladimir Dragoev
0
Eric Boumendil

"Fix: Add Stubs for required members" with IDisposable: follow IDisposable pattern

I use a lot IDisposable. I would be nice if JustCode could follow IDisposable pattern (http://msdn.microsoft.com/en-us/library/b1yfkh5e(v=vs.110).aspx) when I press Alt+Enter on my class to prepare proper implementation of this special interface.
Feature Request by Eric Boumendil Status: New Comments: 0 Last update: 2014-08-07T14:26:24 by Eric Boumendil
0
Displaying items 1 - 10 of 186