- Issue created by @blacksnipe
- 🇧🇪Belgium blacksnipe
For an initial starting point of what I mean, I've added a patch of my changes to get this working.
- 🇧🇪Belgium inge_dt
Can confirm above patch works on Key Value Field version 1.3.0 (and Drupal 10.4.1). Thanks!
- Status changed to RTBC
about 1 month ago 7:43pm 27 June 2025 - 🇨🇦Canada m4olivei Grimsby, ON
We've also had success with the patch in #3. We're running Key Value Field version 1.3.0 (and Drupal 10.5.0).
My only comment is the theme hook is using
key_value
namespace, which doesn't really belong to this module. Although it's already using it for the field formatter, so in that way the ship has sailed. It's also true that the key_value module → doesn't overlap in use case at all, so it's probably fine.Marking RTBC.
- First commit to issue fork.
- 🇺🇸United States japerry KVUO
Looks like the tests will need to be updated/expanded for this to go in. You'll notice a few commits here but that was a mistake, ahh patches ;).. anywho, once those tests are fixed this looks good to me.
- 🇮🇳India divyansh.gupta Jaipur
Hello @japerry,
When i rebased the MR to check if there any other tests that might cause errors in future, the MR became empty and it is not showing any changes that are to be committed, also i cloned the repo and ran pipeline on local but it is passing without any error.
So could you please help here. - 🇮🇳India divyansh.gupta Jaipur
Also when i am going to the commit
fc5be3ffdcca2be09754da0e82cd16c211ae2f6c
then i am able to reproduce the phpunit errors on my local but there is an latest commit which is reverting this commit that is why MR is coming empty should i reset the forked branch to this commitIssue #3437567: Add a template for a key value pair
Thank you!!