Outdated links in error message

[Bogay]

Copied from discord:

Found outdated links in the error message. Perhaps the version string could be extracted from Cargo.toml at compile time to make it more consistent?

fn generate_error_with_docs(span: proc_macro2::Span, message: &str) -> syn::Error {
    syn::Error::new(
        span,
        format!(
            "{message}\n\texpecting #[variant(...)]. See documentation:\n\thttps://docs.rs/gdnative/0.9.0/gdnative/core_types/trait.ToVariant.html#field-attributes"
        ),
    )
}

gdnative/gdnative-derive/src/variant/attr.rs

Lines 72 to 79 in 6dc9721

	fn generate_error_with_docs(span: proc_macro2::Span, message: &str) -> syn::Error {
	syn::Error::new(
	span,
	format!(
	"{message}\n\texpecting #[variant(...)]. See documentation:\n\thttps://docs.rs/gdnative/0.9.0/gdnative/core_types/trait.ToVariant.html#field-attributes"
	),
	)
	}

another one with similar signature:

gdnative/gdnative-derive/src/variant/attr/field.rs

Lines 36 to 43 in 6dc9721

	fn generate_error_with_docs(span: Span, message: &str) -> syn::Error {
	syn::Error::new(
	span,
	format!(
	"{message}\n\texpecting #[variant(...)]. See documentation:\n\thttps://docs.rs/gdnative/0.9.0/gdnative/core_types/trait.ToVariant.html#field-attributes"
	),
	)
	}

[Bogay]

Maybe related: #1039

Should we put latest compatible Godot version in Cargo.toml?

[Bogay]

Oh, the links to godot doc are written in doc comments. So it's harder to generate it 🤔

[chitoyuu]

Doc comments are just sugar for #[doc] attributes so they can be generated using proc-macros. I guess we can also do text-based search & replace in the build script but that's much more of a risky option.