Skip to content

Fix "withSelfDerviation" typo in README.md #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ChrisGarcia-at wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix "withSelfDerviation" typo in README.md #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ Personally I prefer to be explicit about the dependent keys, but it doesn't real

Derivations are processed in the order they are defined, and all `withDerivation` functions produce a new immutable Factory.

If you wish to use an underlying factory's returned value for a given property as _input_ to derive a new value for the property, you can use `withSelfDerviation()`. This will ensure the key you are deriving has a valid starting value (not the case when using `withDerivation`).
If you wish to use an underlying factory's returned value for a given property as _input_ to derive a new value for the property, you can use `withSelfDerivation()`. This will ensure the key you are deriving has a valid starting value (not the case when using `withDerivation`).

Finally, you could instantiate a `Derived<TOwner,TProperty>` for the value of a property inside a `Factory.makeFactory` definition, but the type inference can't help you as much - you'll have to indicate the type of TOwner and TProperty.

Expand Down