Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Shot in the dark here, but could you move those parameters to the method instead?</p> <p>In other words:</p> <pre><code>public Check CreateCheck(bool doTranslateStubData, bool doAttachLogo) { //do the translation... } </code></pre> <p>Do those parameters <em>have</em> to be passed in via the constructor?</p> <p><em>(Note - if your response to this is "there are too many methods for that to be practical", then part of the problem may be that the abstraction is too coarse).</em></p> <hr> <p>Another option (it's really hard to say without understanding the domain model and injection patterns) would be to introduce a parameter object that is itself managed by the injector:</p> <pre><code>public interface ICheckConfiguration { bool AttachLogo { get; } bool TranslateStubData { get; } } </code></pre> <p>Then inject this with the constructor:</p> <pre><code>public CheckTranslator (IEmployeeService empSvc, IPaycheckService paySvc, ICheckConfiguration config) { // etc. } </code></pre> <p>This <em>should</em> be enough. You can then create a concrete <code>CheckConfiguration</code> class that takes those two <code>bool</code> properties in its constructor, and configure your container to create different instances of the parameter object (interface) based on a higher-level DI parameter.</p> <hr> <p>The last thing I think I should mention is that just because you're using DI doesn't mean that <em>everything</em> has to be managed by the container. It's not such a bad thing to create <code>CheckTranslator</code> objects in an ad-hoc fashion if there's only one kind of "translator". As long as the translator still depends on <em>abstractions</em>, which it does here, then maybe you shouldn't be injecting it at all, just let higher-level DI-enabled classes create them ad-hoc.</p>
    singulars
    1. This table or related slice is empty.
    1. PODependency Injection for objects that require parameters
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAaronaught
    1. USAaronaught
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODependency Injection for objects that require parameters
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm too tired to edit my answer again right now but there is one more possibility, which is to use the Abstract Factory Pattern and inject an `[I]CheckTranslatorFactory`. That would be a valid way of creating `CheckTranslator` or `ICheckTranslator` objects of an unknown concrete type, with parameters; instead of injecting the actual translator instance, you inject the factory, and have different factories responsible for creating different translator subtypes. Only really necessary/useful if you intend to use polymorphism for the `CheckTranslator`.
      singulars
      1. PO
      1. USAaronaught
    2. COUse ICheckConfiguration is a good idea. Pass in a Null pattern implementation for the default case, and pass in a real implementation for other cases.
      singulars
      1. PO
      1. USLex Li
    3. COMakes sense. Thanks!
      singulars
      1. PO
      1. USAndrew
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload