feat: wrappers and test helpers

[pavelsmejkal]

Please read CONTRIBUTING.md for additional information on contributing to this repository!

What this PR does / why we need it

• Helpers to make testing easier

• SavePoints and ResetDefinition are solving a problem - the dependency graph is normally evaluated just once and than all the instances are kept. With the Savepoint and ResetDefinition you can redefine certain graph leafs and those will be re-evaluated. The re-evaluation as well cascades to deps that depends on the one that is being reset.

• Instance wrappers

Jira ID

[XX-XX]

Notes for your reviewers

// as to copy definition and but apply different wrappers
root.ContainerA.Dependency2.As(&root.ContainerA.Dependency1).Wrap(
   &root.Wrapper,
   plumber.WrapperFunc(func(s *Dep) *Dep { return s })
)

// localy wrap instance
root.ContainerA.Dependency2.InstanceErrorWrap(&root.Wrapper)
root.ContainerA.Dependency2.InstanceWrap(&root.Wrapper)

// Savepoint creates a restoration point
restore, err := plumber.SavePoint(c, &c.Greeting)
	assert.NilError(t, err)

	t.Run("redefining a cloned dep does not affect the source", func(t *testing.T) {
		// Reset both Greeting and its transitive dependent (Sub.Derived) on the clone so
		// they can be re-defined and re-resolved independently of the original container.
		if err := plumber.ResetDefinition(c, &c.Greeting); err != nil {
			t.Fatalf("ResetDefinition on clone failed: %v", err)
		}

		c.Greeting.Const("howdy")

		assert.Equal(t, "howdy", c.Greeting.Instance())
		assert.Equal(t, "howdy!", c.Sub.Derived.Instance())
	})

	t.Run("Restore point does not affect the source", func(t *testing.T) {
                // Restores to previous state
		restore()
		assert.Equal(t, "hello", c.Greeting.Instance())
		assert.Equal(t, "hello!", c.Sub.Derived.Instance())
	})

// ...

// Disables already defined wrapper
err = plumber.DisableWrapper(c, &c.GreetingWrapper)

[chladnefazole]

Could you also store the examples somewhere, in readme or contributing or whatnot?

It's kind of abstract, I would like to see examples with something from stonehenge or a real use case, but it's interesting, possibly could help with the horrendous giant mocks I had to setup in Content before...

[pavelsmejkal]

Could you also store the examples somewhere, in readme or contributing or whatnot?

It's kind of abstract, I would like to see examples with something from stonehenge or a real use case, but it's interesting, possibly could help with the horrendous giant mocks I had to setup in Content before...

What for ? ... there are 3 examples of what was being added. There is a better documentation on the other PR, so you can approve that one and you will have it.

[chladnefazole]

@pavelsmejkal Which other PR?

[pavelsmejkal]

@pavelsmejkal Which other PR?

#40

There are agent skills for each plumber area with explanation. once merged i will describe same way features introduced in this PR

[chladnefazole]

LGTM

[getoutreach-ci-1]

🎉 This PR is included in version 1.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀