PreferWriteOnlyAttribute validator is not making use of the client capabilities

[yottta]

Terraform CLI and Framework Versions

Terraform v1.11.3 on darwin_arm64

github.com/hashicorp/terraform-plugin-framework-validators from the main branch

Terraform Plugin Framework Code

func (r *writeOnlyResource) Schema(_ context.Context, _ resource.SchemaRequest, resp *resource.SchemaResponse) {
	resp.Schema = schema.Schema{
		Attributes: map[string]schema.Attribute{
			...
			"attr": schema.StringAttribute{
				Optional: true,
				Validators: []validator.String{
					stringvalidator.PreferWriteOnlyAttribute(path.MatchRoot("attr_wo")),
					stringvalidator.ExactlyOneOf(path.MatchRoot("attr_wo")),
				},
			},
			"attr_wo": schema.StringAttribute{
				Optional:  true,
				WriteOnly: true,
				Validators: []validator.String{
					stringvalidator.ExactlyOneOf(path.MatchRoot("attr")),
					stringvalidator.AlsoRequires(path.MatchRoot("attr_wo_version")),
				},
			},
			"has_attr_wo": schema.BoolAttribute{
				Computed: true,
			},
			"attr_wo_version": schema.Int32Attribute{
				Optional: true,
			},
		},
	}
}

Terraform Configuration

terraform {
  required_providers {
    provs = {
      source = "edu/provs"
    }
  }
}

provider "provs" {
  path = "/var/tmp/custom_tf_provider"
}

resource "provs_write_only_test" "test" {
  attr = "attr val"
}

Expected Behavior

Have this warning printed:

Actual Behavior

The warning is not shown.

Steps to Reproduce

1. terraform plan

Logs

No response

Additional Information

This is due to the configuration of the validator. The client capabilities are not passed into the validator struct and the writeOnly capability is always false. Due to this, the validator is always skipped.

I already have a fix for this, but as suggested in the contribution guide, before opening a PR, I opened an issue first to understand if this behavior is actually intended for the moment or it is truly a bug.

Code of Conduct

• I agree to follow this project's Code of Conduct

[austinvalle]

Hey there @yottta 👋🏻 , thanks for reporting the issue!

That definitely looks like a bug, so if you already have a PR ready to open, we can review/merge, then release a new patch version of the validators Go module 👍🏻.

[yottta]

Hey there @yottta 👋🏻 , thanks for reporting the issue!

That definitely looks like a bug, so if you already have a PR ready to open, we can review/merge, then release a new patch version of the validators Go module 👍🏻.

Thanks for your reply @austinvalle 🙌

#283 is containing the changes.
Right now, I cannot handle the CLA signing. I can do it only next week. In the meantime, if you want to apply the changes yourself, I would be more than happy to see this fixed.
Thanks

[austinvalle]

No worries, our entire team is busy ATM, so we won't be able to release until next week regardless.

If you (or any other visitors of this issue) need an immediate fix you can always bring the validator code into your provider repo's code base for the short term.

[yottta]

Fixed by #287.
Thanks for the help.