Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/Numpsy/FSharpLint below:

Numpsy/FSharpLint: Lint tool for F#

FSharpLint is a static analysis tool for F#. Like many other software linters, it analyzes your source code (using both typed and untyped syntax trees) and highlights any violations of defined F# coding rules. There are various kinds of rules:

• Conventions: ensures that your API members follow project- or solution-wide naming conventions.
• Smells: warns about logic that may pose maintainability problems or potential downsides.
• Formatting: checks that code is indented and structured according to specified cosmetic standards.

The tool is configurable via JSON and can be run as a console app or as an MSBuild task. It also provides an interface for easy integration into other software.

The project aims to let the user know of problems through matching user defined hints a la HLint, and also by using custom rules written in F# similar to the rules in Mascot and StyleCop.

The tool in use (running as an MSBuild task with TreatWarningsAsErrors set to true):

FSharpLint can be used in several ways:

• Running as dotnet tool from command line.
• In VS Code using the Ionide-FSharp plugin.
• In Visual Studio using the F# Lint extension.
• As an MSBuild Task.
• In other editors through FsAutoComplete Language Server

The docs contain an overview of the tool and how to use it, including a list of the available rules for linting.

1. Make sure you've installed the .NET version defined in global.json
2. Run dotnet tool restore to install all developer tools required to build the project
3. Run make to build (which executes the Build target from the FAKE-based build script)
4. To run tests use make check
5. To build documentation use make docs

1. Make sure you've installed the .NET version defined in global.json
2. Run dotnet tool restore to install all developer tools required to build the project
3. Run dotnet fsi build.fsx to build default target of build script
4. Build documentation to make sure everything is fine with dotnet fsi build.fsx -t Docs
5. Go to docs folder cd docs and start Fornax in watch mode dotnet fornax watch
6. Your documentation should be now accessible on localhost:8080 and will be regenerated on every file save

Please read the Releasing Guidelines if you're a maintainer.

Bug reports, feature requests, and pull requests are very welcome! Please read the Contribution Guidelines to get started.

The project is licensed under MIT. For more information on the license see the LICENSE file.

• @duckmatt
• @knocte
• @jgardella

The default maintainer account for projects under "fsprojects" is @fsprojectsgit - F# Community Project Incubation Space (repo management)

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4