Struct GradleFormatter 

pub struct GradleFormatter;

Trait Implementations

impl DiagnosticMessages for GradleFormatter

fn yanked_message(&self) -> &'static str

Message for yanked/deprecated versions in diagnostics.

fn yanked_label(&self) -> &'static str

Label for yanked versions in hover.

fn deprecated_message(&self) -> &'static str

Message for a package-level deprecation/abandonment diagnostic (issue #205).

fn deprecated_label(&self) -> &'static str

Label for a deprecated package in hover.

impl DiagnosticPolicy for GradleFormatter

fn strict_semver_prerelease_exclusion(&self) -> bool

Whether this ecosystem’s requirement/version syntax follows strict SemVer 2.0.0 pre-release semantics: a pre-release version (X.Y.Z-pre) is excluded from matching requirement unless requirement itself pins to the same X.Y.Z tuple with a pre-release tag — the rule Cargo’s semver crate and npm’s node-semver both implement, and that compile_requirement’s matcher inherits from its underlying comparator.

fn supports_package_rename(&self) -> bool

Whether this ecosystem’s deprecation payload (crate::Deprecation::replacement) is safe to offer as a “Replace with X” rename quickfix.

fn yanked_diagnostic_applies_to( &self, _dep: &dyn Dependency, _requirement: &VersionReq, ) -> bool

Whether the “requirement satisfiable only by a yanked version” diagnostic (crate::lsp_helpers::requirement_matches_only_yanked) should evaluate requirement at all for this ecosystem.

impl OsvNaming for GradleFormatter

fn osv_package_name(&self, dep: &dyn Dependency) -> Option<String>

OSV.dev’s canonical spelling for dep’s package name, or None if this dependency cannot be mapped (e.g. a non-GitHub Swift package).

fn osv_version_to_native(&self, version: &str) -> String

Converts a version string as it appears in an OSV advisory record (e.g. crate::osv::Advisory::fixed_versions) into this ecosystem’s own version namespace, as used in manifests and by the registry.

fn osv_version(&self, version: &str) -> String

Rewrites a native-ecosystem version string into the spelling OSV.dev’s SEMVER range matching expects.

impl PackageNaming for GradleFormatter

fn validate_package_name(&self, name: &str) -> Result<(), InvalidPackageName>

Validates a Gradle coordinate’s group:artifact shape and character set.

Gradle resolves through deps_maven::MavenCentralRegistry and shares Maven’s groupId:artifactId coordinate shape (see deps-gradle/src/ecosystem.rs), so this mirrors deps_maven’s MavenFormatter::validate_package_name exactly, reusing is_safe_maven_coordinate_segment rather than duplicating it — letting the “Invalid package name” diagnostic surface the accurate reason instead of the generic “Unknown package” a registry-side rejection produces (#375).

Unlike Maven’s ${property}-specific is_unresolved, this uses Gradle’s own is_unresolved, which also short-circuits on an unresolved $var/${var} reference or Gradle-catalog-alias placeholder — valid Gradle syntax, not a malformed coordinate.

Errors

Returns InvalidPackageName if name has no : separator, or if either the group or artifact segment fails is_safe_maven_coordinate_segment — but never when name is unresolved per is_unresolved, which is accepted instead.

fn normalize_package_name(&self, name: &PackageName) -> String

Normalize package name for lookup (default: identity).

impl PackageRendering for GradleFormatter

fn format_version_replacing( &self, version: &ConcreteVersion, current: &str, ) -> String

Preserves Gradle’s rich-version strict/preferred shorthand ({strictlyVersion}!!{preferredVersion}) when current carries it — a bare format_version_for_text_edit replacement would otherwise silently downgrade a strict constraint to a normal one.

Only the degenerate suffix form (1.2.3!!, no preferredVersion) is rewritten — to {version}!! — since the strict pin itself is what “update version” means to bump there, and there is nothing else in the requirement to preserve. The full infix form ([1.7,1.8[!!1.7.25) is left unchanged rather than rewriting the preferredVersion half: since Gradle’s strict constraint always wins conflict resolution, bumping the preference to a version outside the hand-written strict range (a likely outcome for “update to latest”) would silently write a no-op edit that looks like an update but changes nothing — worse than the original silently-dropped-marker bug, since the manifest now reads as though it were updated. There is no single rewrite that is safe in general without inspecting the strict range’s bounds, which is out of scope here. current is trimmed before the marker check for the same un-trimmed-catalog-value reason as strip_strict_marker above. A no-op return here is safely excluded from deps-core’s collect_update_all_edits (“Update N outdated dependencies” lens) by its own no-op guard.

fn format_version_for_text_edit(&self, version: &ConcreteVersion) -> String

Format version string for code action text edit.

fn package_url(&self, name: &PackageName) -> String

Get package URL for hover markdown.

fn format_version_replacing_for( &self, _dep: &dyn Dependency, version: &ConcreteVersion, current: &str, ) -> String

Like format_version_replacing, but also carries the dependency identity version/current apply to.

fn suppress_package_url(&self, source: &DependencySource) -> bool

Whether hover should omit Self::package_url’s heading link for a dependency resolved against source.

fn is_position_on_dependency( &self, dep: &dyn Dependency, position: Position, ) -> bool

Detect if cursor position is on a dependency for code actions.

impl RequirementResolution for GradleFormatter

fn compile_requirement( &self, requirement: &VersionReq, ) -> Option<Box<dyn RequirementMatcher>>

Uses compile_requirement_unless (see that function and deps_core::lsp_helpers::RequirementResolution::compile_requirement for the shared “undecidable” contract).

The undecidable predicate rejects a malformed range (leading [/(/] but crate::range::parse_range fails) — checked unconditionally, first, before any other branch: without this guard ahead of the AlwaysSatisfied/dynamic-prefix short-circuits below, a malformed bracket range that also happens to end in + (e.g. "[1.0,2.0]+") would be misclassified as a dynamic prefix — which decides Some(false) for every real candidate — instead of correctly suppressing the check.

#249 review (M4): this is a separate branch-order copy from gradle_version_matches above — see the note on that function before reordering either one.

fn version_satisfies_requirement( &self, version: &ConcreteVersion, requirement: &str, ) -> bool

Check if a version satisfies a requirement string.

fn requirement_is_unresolved(&self, requirement: &VersionReq) -> bool

Whether requirement could not be resolved to a concrete version constraint (e.g. an unexpanded property/variable placeholder rather than a real version or range).

fn is_requirement_up_to_date( &self, requirement: &VersionReq, latest: &ConcreteVersion, ) -> bool

Whether an unresolved dependency (no lock-file version) should be reported as up to date against latest, given its declared requirement.

fn requirement_status( &self, requirement: &VersionReq, latest: &ConcreteVersion, ) -> RequirementStatus

Tri-state variant of is_requirement_up_to_date that distinguishes “confirmed up to date” from “could not be resolved, so we don’t know.”

fn requirement_status_for( &self, dep: &dyn Dependency, requirement: &VersionReq, latest: &ConcreteVersion, ) -> RequirementStatus

Like requirement_status, but also hands the ecosystem the dependency itself — for an ecosystem whose requirement text alone is ambiguous between two shapes with different resolution rules, and which already computed the disambiguating classification once, at parse time, onto the dependency (deps-gitlab-ci’s PinStyle, #466 review M-c: a bare "1.2" is Partial under its component: pin grammar but Branch under its simpler project: ref grammar — indistinguishable from the text alone).

fn requirement_is_undecidable_given_available( &self, _requirement: &VersionReq, _available: &[ConcreteVersion], ) -> bool

Whether this ecosystem’s registry can silently omit a published version from available in a way indistinguishable from “never published” — and, if so, whether requirement names a version-space region that specific omission could explain, given the versions actually observed in available.

fn manifest_requirement_is_resolved_version(&self, dep: &dyn Dependency) -> bool

Whether dep’s manifest version-requirement line is itself the exact version already selected — never a range.

impl SourcePolicy for GradleFormatter

fn can_resolve_source(&self, source: &DependencySource) -> bool

Whether this ecosystem’s registry can resolve version data for source.

fn source_is_public_registry_content(&self, source: &DependencySource) -> bool

Whether source’s content is exactly the default public registry’s — safe to treat as such for OSV vulnerability scanning, cache-key signature construction, and hover heading links.