c# - Customizations vs Residue collectors -


i don't grasp difference between customizations , residue collectors.

according documentation, if register customization can build, exampleclass handle requests type were not handled other builders. if register residue collector type exampleclass handle requests, were not handled (other) builders

where's difference?

tl;dr
that's valid question. difference between 2 priority, order in they're given chance handle requests. customizations first, while residue collectors last.

autofixture, @ core, consists of chain of responsibility each node in pipeline called specimen builder. these builders organized in 3 categories, determine position in chain:

  1. customizations
  2. engine
  3. residue collectors

specimen builders higher in chain handle incoming requests first, effectively overriding further down.

customizations typically ad-hoc specimen builders created user handle kind of requests in particular way. hence, they're given highest priority.

engine built-in specimen builders come autofixture. handle primitive types such strings, numbers , dates.

residue collectors specimen builders lowest priority , catch requests can't handled other builder. they're typically used fall-back strategy.


Comments

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

SQL: Divide the sum of values in one table with the count of rows in another -