Returns an iterator over the fixes in the map, along with the file path.

Inserts `rule` into the set. ## Examples ```rust # use fortitude_linter::registry::{Rule, RuleSet}; let mut set = RuleSet::empty(); assert!(!set.con

Returns the number of rules in this set. ## Examples ```rust # use fortitude_linter::registry::{Rule, RuleSet}; assert_eq!(RuleSet::empty().len(), 0

Returns `Some` if this set has an option that resolves to `name` and `None` otherwise. The name can be separated by `.` to find a nested option. ##

Return the symbol with the given name if it exists

Returns an iterator over the rules in this set. ## Examples ```rust # use fortitude_linter::registry::{Rule, RuleSet}; let set = RuleSet::from_rules

Parses a match arm such as `(Pycodestyle, "E112") => (RuleGroup::Preview, rules::pycodestyle::rules::logical_lines::NoIndentedBlock),`

Return the number of bytes in the source code.

TODO (peter): Don't return `Option`? Returns the [`Rule`] corresponding to the diagnostic message.

Run [`check_path`] on a Fortran file in the `resources/test/fixtures` directory.

Wrapper around `std::fs::read_to_string` with some extra error checking. Check that the file length is representable as `u32` so that we don't need t

Removes `rule` from the set. ## Examples ```rust # use fortitude_linter::registry::{Rule, RuleSet}; let mut set = RuleSet::from_rules(&[Rule::Missing

Returns rules matching the selector, taking into account rule groups like preview and deprecated.

Returns an iterator over the fixes in the map.

Return `true` if the source code is empty.

Sends a request to display an error to the client with a formatted message. The error is sent in a `window/showMessage` notification. Logs an error i

Returns `true` if this set contains no rules, `false` otherwise. ## Examples ```rust # use fortitude_linter::registry::{Rule, RuleSet}; assert!(Rule

Convert any path to an absolute path (based on the current working directory).

Returns `true` if the message contains a [`Fix`].

Return `true` if the given candidates should be ignored based on the exclusion criteria.

Extract the [`Settings`] from a given `fortitude.toml` and process the configuration with the given [`ConfigurationTransformer`].

Return all matching rules, regardless of rule group filters like preview and deprecated.

Computes the start source location for the message.

Returns the [`Fix`] for the message, if there is any.

Return offset ranges for filename, if it exists Requires a `SourceFile` to turn line numbers into offsets

Returns true if `self` and `other` contain at least one common rule. ## Examples ```rust # use fortitude_linter::registry::{Rule, RuleSet}; let set_1

Converts the key back into its original URL.

Resolve `--foo` and `--no-foo` arguments

Return the path to the `fpm/fortitude/pyproject.toml` file in a given directory. Adapted from ruff

Creates a document snapshot with the URL referencing the document to snapshot.

Returns all code actions kinds that the server currently supports.

Apply a series of fixes.

Returns the message body to display to the user.

Returns the [`SourceFile`] which the message belongs to.