Namespace ToSic.Eav.LookUp
Sometimes objects need to get values from the context - like...
- a URL Parameter
- the current date/time
- an App Setting or Resource
etc. This is done through ToSic.Eav.LookUp.ILookUp objects.
In many cases, we need to look up a few - like when we have a configuration made with Tokens.
These would look like [App:Path] or [QueryString:Ui].
The tool which takes a list of these and looks all of them up is the ToSic.Eav.LookUp.ILookupEngine.
Tip
Read more about this in [](Abyss.Parts.LookUp.Index
Classes
LookUpBase
Base Class to create your own LookUp Class - used by all Look-Ups.
Read more about this in LookUp System
LookUpInDataTarget
Base Class to create your own LookUp Class - used by all Look-Ups.
Read more about this in LookUp System
LookUpInDictionary
Look Up values from a .net dictionary. Case-Insensitive.
Read more about this in LookUp System
LookUpInEntity
Get Values from an IEntity.
Read more about this in LookUp System
LookUpInLookUps
This Value Provider chains two or more LookUps and tries one after another to deliver a result
It's mainly used to override values which are given, by a special situation.
Read more about this in LookUp System
LookUpInNameValueCollection
Look-Up helper to get something from a standard .net NameValueCollection.
Read more about this in LookUp System
LookUpIn<T>
Interfaces
ILookUp
A key-value map which resolves keys like "SortOrder" to "asc".
It's usually used to get pre-stored configuration or to get settings from the context.
Read more about this in LookUp System
ILookUpEngine
Resolves Configurations from LookUps. Common use is for configurable DataSources
ILookUpEngineResolver
An object implementing this interface can provide an engine for the current context.
It's important so that code can easily ask for the current engine, but that the
real implementation is dependency-injected later on, as each environment (DNN, Nop, etc.)
can provide different initial engines.
Read more about this in LookUp System