Angular 2 и внедрение зависимостей

Содержание:

Container Commands

setreceivingcontainer

The ‘setreceivingcontainer’ command allows you to set the container that
will be used to place the items frem another container using the
or
command. When the command is used, a targeting cursor will come up so
you target the container you want to use.

emptycontainer
(speed)

The ’emptycontainer’ command will move all items in targeted container
to the container set by the
command or your backpack if the receiving container is not set. Where
the ‘speed’ is the milliseconds to pause between moves.

Note: The client does not update until the ’emptycontainer’ command
is complete. However, the items are being moved, you just don’t see the
results until the client updates its view. I recommend a speed of 500-1000
on shards that frown on this feature. This will make it look realistic
enough to do away with any concerns they may have. Before the ’emptycontainer’
command can successfully run, you must first open the container you want
to empty.

Menu commands

In the context of Injection, a ‘menu’ (or menu gump) is one of the rectangular
windows that usually appears in the top left of your screen when you are
selecting an item to craft. The gumps that perform more complex actions such
as rune books are not considered to be ‘menus’. An example menu is:

Please note: the commands in this section are experimental and have not
been tested properly yet. Do not be surprised if they do not behave as expected.

An example of the use of the ‘waitmenu’ and ‘choosemenu’ commands to automatically
choose a lesser heal potion from a menu is:

Say:
Double click a mortar
Target a reagent
Say:

See the descriptions of these commands (below) for an explanation.

waitmenu (partial prompt)

This is the first command you should use if you want to automatically
select an option from a gump menu. In the above example, the word ‘potion’
after the ‘waitmenu’ command specifies part of the prompt string
that is normally displayed at the top of the menu window. This is just used
to make sure the correct menu is open. In this case, the actual prompt message
might be «What sort of potion do you want to make?» but you need only specify
a part of this string (but case sensitively).

Please be aware that after you target the reagent, the menu for selecting
a type of potion will not appear on your screen. Instead,
a message should be printed at the bottom of your screen saying . At this point, you may type either the
‘choosemenu’ command or the ‘cancelmenu’ command.

choosemenu (partial description)

The ‘choosemenu’ command may be used only after successfully using the
‘waitmenu’ command specified above. If you can see a menu visible on the
client screen, you may not use the ‘choosemenu’ command to
select an option from it.

The ‘partial description’ argument specifies part of the description
string normally displayed at the bottom of the menu window. In the example
above, the string ‘Lesser Heal’ was used to identify which option to select
from the menu. Note that if the partial description contains a space, you
must enclose it in single quotes (as shown in the example).

If the description you specify cannot be found in the current menu, an
error message will be displayed and the current menu will be cancelled.
.

cancelmenu

The ‘cancelmenu’ command may be used only after successfully using the
‘waitmenu’ command specified above. It simply closes the (invisible) menu
that is currently open.

Example

simple injection:

var injecting = require('injecting');
var app = injecting();
app.register('name', 'jack');
app.register('person', function(name) {
    this.name = name;
});

app.invoke(function(person) {
    console.log(person.name); // jack
});

recursive injection:

var injecting = require('injecting');
var app = injecting();
app.register('place', 'pacific');
app.register('cat', function() {
    this.name = "white cat";
});
app.register('person', function(cat) {
    this.name = "robot";
    this.pet = cat;
});
app.register('story', function(place, person){
    return {
        place: place,
        person: person.name,
        pet: person.pet.name
    };
});
app.invoke(function(story){
    console.log(story);
    /* should be
    {
        place: 'pacific',
        person: 'robot',
        pet: 'white cat'
    };
    */
});

Example with interfaces

Interfaces don’t have type information at runtime, so we need to decorate them
with so the container knows how to resolve them.

// SuperService.ts
export interface SuperService {
  // ...
}

// TestService.ts
import {SuperService} from "./SuperService";
export class TestService implements SuperService {
  //...
}

// Client.ts
import {injectable, inject} from "tsyringe";

@injectable()
export class Client {
  constructor(@inject("SuperService") private service: SuperService) {}
}

// main.ts
import "reflect-metadata";
import {Client} from "./Client";
import {TestService} from "./TestService";
import {container} from "tsyringe";

container.register("SuperService", {
  useClass: TestService
});

const client = container.resolve(Client);
// client's dependencies will have been resolved

The following is a list of features we explicitly plan on not adding:

Property Injection

Contributing

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.

Targeting Commands

Please note: the commands in this section are experimental and have not
been tested properly yet. Do not be surprised if they do not behave as expected.

An example of the use of the ‘waittarget’ and ‘target’ commands to automatically
target a heal potion and place it in a keg:

Say:
Double click a heg
Say:

See the descriptions of these commands (below) for an explanation.

waittarget

This is the first command you should use if you want to automatically
target an item. This tells injection you will be issuing a target command.

Please be aware that after you issue a command that would bring up a
target cursor , the targeting cursor will not appear on your screen
. Instead, a message should be printed at the bottom of your screen saying
. At this point, you may type either the
‘target’ command or the ‘canceltarget’ command.

targettype (identifier)

The ‘targettype’ command is used like the
command except it targets the item type instead of double clicking it..
It’s arguments are a registered object type name or index and optionally
a color index.

targetobject (identifier or serial)

The ‘targetobject’ command is used like the
command except it targets the item instead of double clicking it.. It’s
arguments are a registered object name or serial number.

Иерархическое внедрение зависимостей

Я уже упоминал, что Angular2-приложение — это дерево компонентов. И у каждого компонента есть свой роутер и инжектор. Таким образом дерево инжекторов и компонентов параллельны.

Какие плюсы даёт такой подход? Например, теперь легко можно настроить один и тот же сервис по-разному, в зависимости от компонента, в который он внедряется. При этом, можно не бояться как-то повлиять на другие компоненты выше или на том же уровне иерархии, так как они будут использовать другие экземпляры того же сервиса. Компонент теперь не зависит от того, как был сконфигурирован какой-то сервис. Если компоненту нужен отдельный экземпляр сервиса, он просто добавляет его в секцию .

Заметьте, в коде сервисов нет нигде упоминания о провайдерах. Мы не можем зарегистрировать какой-то провайдер в рамках какого-нибудь сервиса. Если в сервис внедряется другой сервис, его провайдер регистрируется в каком-то компоненте. Мы не сможем внедрить сервис без компонента. Таким образом, ещё раз подчёркивается компонентный подход всего фреймворка: сервисный слой стал вторичным, на первое место вышли компоненты. И у каждого компонента могут быть свои личные изолированные от других экземпляры сервисов.

Разумеется, ангуляр не создаёт для каждого компонента отдельный инжектор. Это было бы довольно неэффективно. Но в любом случае, каждый компонент имеет свой инжектор, даже если делит его с другим компонентом.

Как происходит выбор нужного экземпляра зависимости? У каждого компонента зависимость либо прописана в секции , либо должна быть найдена выше по иерархии. Для инжектора корневого компонента выше по иерархии стоит только глобальный инжектор, который создаётся при вызове функции .
Если поле не пустое, инжектор компонента становится равным результату выполнения статического метода , который резолвит переданный массив провайдеров и создаёт новый экземпляр инжектора. У каждого инжектора есть поле , которое содержит ссылку на родительский инжектор. Если компоненту требуется зависимость, инжектор компонента пытается найти нужную у себя. Если не находит, пытается найти в родительских инжекторах вплоть до корневого.

Вот пример того, как работают инжекторы с иерархией:

Тут 2 сервиса и 2 компонента. В родительском компоненте регистрируются 2 сервиса ( и ), в дочернем — только . Если понажимать на кнопки , то одинаковые массивы будут только у , так как дочерний компонент, не найдя у себя зависимость использует инстанс, полученный из родительского компонента. А вот экземпляр у дочернего компонента создастся новый. Поэтому дочерний компонент будет писать в свой экземпляр, а родительский — в свой.

Означает ли это, что сервисы в Angular2 не являются синглтонами? В конкретном инжекторе не может быть больше 1-го инстанса сервиса. Но так как самих инжекторов может быть несколько, то и разных инстансов одного и того же сервиса во всём приложении может быть больше одного.

Where to Register Services

Services must be registered to a container before they are used. The typical registration approach will differ depending upon whether you are using or not.

The following view controller class is used in addition to the protocols and classes above in the examples below.

class PersonViewController: UIViewController {
    var person Person?
}

With SwinjectStoryboard

Import SwinjectStoryboard at the top of your swift source file if you use Swinject v2 in Swift 3.

// Only Swinject v2 in Swift 3.
import SwinjectStoryboard

Services should be registered in an extension of if you use . Refer to the project page of SwinjectStoryboard for further details.

extension SwinjectStoryboard {
    @objc class func setup() {
        defaultContainer.register(Animal.self) { _ in Cat(name: "Mimi") }
        defaultContainer.register(Person.self) { r in
            PetOwner(pet: r.resolve(Animal.self)!)
        }
        defaultContainer.register(PersonViewController.self) { r in
            let controller = PersonViewController()
            controller.person = r.resolve(Person.self)
            return controller
        }
    }
}

Without SwinjectStoryboard

If you do not use to instantiate view controllers, services should be registered to a container in your application’s . Registering before exiting will ensure that the services are setup appropriately before they are used.

class AppDelegate: UIResponder, UIApplicationDelegate {
    var window UIWindow?
    let container Container = {
        let container = Container()
        container.register(Animal.self) { _ in Cat(name: "Mimi") }
        container.register(Person.self) { r in
            PetOwner(pet: r.resolve(Animal.self)!)
        }
        container.register(PersonViewController.self) { r in
            let controller = PersonViewController()
            controller.person = r.resolve(Person.self)
            return controller
        }
        return container
    }()

    func application(
        _ application: UIApplication,
        didFinishLaunchingWithOptions launchOptions: ? = nil) -> Bool {

        // Instantiate a window.
        let window = UIWindow(frame: UIScreen.main.bounds)
        window.makeKeyAndVisible()
        self.window = window

        // Instantiate the root view controller with dependencies injected by the container.
        window.rootViewController = container.resolve(PersonViewController.self)

        return true
    }
}

Notice that the example uses a convenience initializer taking a closure to register services to the new instance of .

Framework-provided services

The method is responsible for defining the services that the app uses, including platform features, such as Entity Framework Core and ASP.NET Core MVC. Initially, the provided to has services defined by the framework depending on . It’s not uncommon for an app based on an ASP.NET Core template to have hundreds of services registered by the framework. A small sample of framework-registered services is listed in the following table.

Service Type	Lifetime
Microsoft.AspNetCore.Hosting.Builder.IApplicationBuilderFactory	Transient
Microsoft.AspNetCore.Hosting.IApplicationLifetime	Singleton
Microsoft.AspNetCore.Hosting.IHostingEnvironment	Singleton
Microsoft.AspNetCore.Hosting.IStartup	Singleton
Microsoft.AspNetCore.Hosting.IStartupFilter	Transient
Microsoft.AspNetCore.Hosting.Server.IServer	Singleton
Microsoft.AspNetCore.Http.IHttpContextFactory	Transient
Microsoft.Extensions.Logging.ILogger<TCategoryName>	Singleton
Microsoft.Extensions.Logging.ILoggerFactory	Singleton
Microsoft.Extensions.ObjectPool.ObjectPoolProvider	Singleton
Microsoft.Extensions.Options.IConfigureOptions<TOptions>	Transient
Microsoft.Extensions.Options.IOptions<TOptions>	Singleton
System.Diagnostics.DiagnosticSource	Singleton
System.Diagnostics.DiagnosticListener	Singleton

Bugs and Troubleshooting

Some of the common problems you may encounter when installing and using
Injection are:

ILaunch error: «This client verion is not supported. (No patch information
for selected client.)»

If you are trying to use a new client (higher than 3.0.0 or UOTD),
you may need to get an updated Ignition.cfg from the
Ignition
website. If the client is a very recent patch, you may need to wait a
couple of days for the new Ignition.cfg to be released. In the mean time,
you can try to get a previous client version from
this site
, or from Paigelore
.
This probably means that the the client path you selected was not
valid. Check that the path displayed in the Injection Launcher main window
is correct.
This error may occur if you run ilaunch.exe from a directory that
does not contain Injection. If you created a shortcut to run ILaunch, make
sure that the working directory (the «Start in» field) is the directory
containing injection.dll.
If the client exits just after starting, with no error message…

This may also be caused by an error while loading Injection. In particular,
running two copies of Injection will cause the second client to exit immediately
after starting. Injection does not (yet) support running two clients at
once, but you can still run one client with Injection, and another without.
This may be caused by a bug in the client, or a bug in Injection
(among other causes). Look in the «injection_log.txt» file for information
about the possible causes of the crash. If you think the crash may be caused
by a bug in Injection, please submit a bug report to the
Bug Tracker
. If you can figure out how to reproduce the bug, include steps to do
so in your bug report, because this will greatly reduce the time it will
take for the bug to be fixed.
PLEASE NOTE: since I do not have UO:TD, Injection
has not been tested AT ALL with Third Dawn. It might work,
but the chances are there will be problems.

The following error messages only appear when using Ignition:

Ignition error: «Patching of target failed: Invalid patch information
(checksum=XXXXXXXX, length=XXXXXX).»

If you are trying to use a new client (higher than 3.0.0 or UOTD),
you may need to get an updated Ignition.cfg from the
Ignition
website. If the client is a very recent patch, you may need to wait a
couple of days for the new Ignition.cfg to be released. In the mean time,
you can try to get a previous client version from
this site
, or from Paigelore
.
Ignition error: «Patching of target failed: Failed to load modules
(module=injection.dll).»

This error means that there was a problem finding the Injection
DLL. Check to make sure the file «injection.dll» is in the same directory
as Ignition, and that the line you added to Ignition.cfg is spelt correctly.
Ignition error: «Patching of target failed: Failed to install module
(module=injection.dll).»

Anti Minification

The code shows above does not robust enough when our source code is minified. For example:

app.register('person', 'jack');
app.invoke(function(person) {
  console.log(person);
});
// will be minified as
app.invoke(function(a) {
  console.log(a);
});
// it will lead to app crush in such case since `a` is not registered.

Solution

There are several method to avoid minification problem. Look at the code below:

// invoke a function with predefined injections
app.invoke('person', 'job', function(p, j) {
  console.log(p, j);
});
// register a dep with predefined injections
app.register('person', 'name', 'age', function (n, a) {
  return {name: n, age： a};
});

Please refer to the test cases for more examples.

Step-by-step example

# Import the inject module.
import inject


# `inject.instance` requests dependencies from the injector.
def foo(bar):
    cache = inject.instance(Cache)
    cache.save('bar', bar)


# `inject.params` injects dependencies as keyword arguments or positional argument. 
# Also you can use @inject.autoparams in Python 3.5, see the example above.
@inject.params(cache=Cache, user=CurrentUser)
def baz(foo, cache=None, user=None):
    cache.save('foo', foo, user)

# this can be called in different ways:
# with injected arguments
baz('foo')

# with positional arguments
baz('foo', my_cache)

# with keyword arguments
baz('foo', my_cache, user=current_user)


# `inject.param` is deprecated, use `inject.params` instead.
@inject.param('cache', Cache)
def bar(foo, cache=None):
    cache.save('foo', foo)


# `inject.attr` creates properties (descriptors) which request dependencies on access.
class User(object):
    cache = inject.attr(Cache)
            
    def __init__(self, id):
        self.id = id

    def save(self):
        self.cache.save('users', self)
    
    @classmethod
    def load(cls, id):
        return cls.cache.load('users', id)


# Create an optional configuration.
def my_config(binder):
    binder.install(my_config2)  # Add bindings from another config.
    binder.bind(Cache, RedisCache('localhost:1234'))

# Configure a shared injector.
inject.configure(my_config)


# Instantiate User as a normal class. Its `cache` dependency is injected when accessed.
user = User(10)
user.save()

# Call the functions, the dependencies are automatically injected.
foo('Hello')
bar('world')

Пишем подопытного

Программа очень примитивна. При нажатие Enter она просто выдаёт содержимое буфера на экран. Содержимое буфера жестко прописано в памяти и нигде не меняется.

Вариант 1. Присоединись к сообществу «Xakep.ru», чтобы читать все материалы на сайте

Членство в сообществе в течение указанного срока откроет тебе доступ ко ВСЕМ материалам «Хакера», увеличит личную накопительную скидку и позволит накапливать профессиональный рейтинг Xakep Score!
Подробнее

Вариант 2. Открой один материал

Заинтересовала статья, но нет возможности стать членом клуба «Xakep.ru»? Тогда этот вариант для тебя!
Обрати внимание: этот способ подходит только для статей, опубликованных более двух месяцев назад.

Я уже участник «Xakep.ru»

Decorators

injectable()

Class decorator factory that allows the class’ dependencies to be injected at
runtime. TSyringe relies on several decorators in order to collect metadata about classes
to be instantiated.

import {injectable} from "tsyringe";

@injectable()
class Foo {
  constructor(private database: Database) {}
}

// some other file
import "reflect-metadata";
import {container} from "tsyringe";
import {Foo} from "./foo";

const instance = container.resolve(Foo);

singleton()

Class decorator factory that registers the class as a singleton within the
global container.

import {singleton} from "tsyringe";

@singleton()
class Foo {
  constructor() {}
}

// some other file
import "reflect-metadata";
import {container} from "tsyringe";
import {Foo} from "./foo";

const instance = container.resolve(Foo);

autoInjectable()

Class decorator factory that replaces the decorated class’ constructor with
a parameterless constructor that has dependencies auto-resolved.

Note Resolution is performed using the global container.

import {autoInjectable} from "tsyringe";

@autoInjectable()
class Foo {
  constructor(private database?: Database) {}
}

// some other file
import {Foo} from "./foo";

const instance = new Foo();

Notice how in order to allow the use of the empty constructor , we
need to make the parameters optional, e.g. .

inject()

Parameter decorator factory that allows for interface and other non-class
information to be stored in the constructor’s metadata.

import {injectable, inject} from "tsyringe";

interface Database {
  // ...
}

@injectable()
class Foo {
  constructor(@inject("Database") private database?: Database) {}
}

injectAll()

Parameter decorator for array parameters where the array contents will come from the container.
It will inject an array using the specified injection token to resolve the values.

import {injectable, injectAll} from "tsyringe";

@injectable
class Foo {}

@injectable
class Bar {
  constructor(@injectAll(Foo) fooArray: Foo) {
    // ...
  }
}

scoped()

Class decorator factory that registers the class as a scoped dependency within the global container.

English[edit]

An injection (relation on sets in mathematics)

Etymologyedit

Borrowed from Middle French , from Latin . The mathematical sense is from French , introduced by Nicolas Bourbaki in their treatise Éléments de mathématique.

Nounedit

injection ( and , plural )

The act of injecting, or something that is injected.
A specimen prepared by injection.
(category theory) A morphism from either one of the two components of a coproduct to that coproduct.
(construction) The act of inserting materials like concrete grout or gravel by using high pressure pumps.
() The supply of additional funding to a person or a business.

The troubled business received a much-needed cash injection.
(mathematics) A relation on sets (X,Y) that associates each element of Y with at most one element of X.
() The insertion of program code into an application, URL, hardware, etc.; especially when malicious or when the target is not designed for such insertion.

a SQL injection exploit allowing a malicious user to modify a database query
(space science) The act of putting a spacecraft into a particular orbit, especially for changing a stable orbit into a transfer orbit, e.g. trans-lunar injection

2015, Henry L. Richter, America’s Leap Into Space
It had been determined that one of the whip turnstile antennas had broken off from Explorer 1 shortly after injection into orbit, so these were eliminated.

.
(set theory) A function that maps distinct x in the domain to distinct y in the codomain; formally, a f: X → Y such that f(a) = f(b) implies a = b for any a, b in the domain.
(specifically, medicine) Something injected subcutaneously, intravenously, or intramuscularly by use of a syringe and a needle.
(steam engines) The act of throwing cold water into a condenser to produce a vacuum.
(steam engines) The cold water thrown into a condenser to produce a vacuum.

Hyponymsedit

direct injection
sperm injection

(computing) Insertion of program code into an application, URL, etc.

broker injection
code injection
constructor injection
email injection
fault injection
network injection
packet injection
SQL injection

(construction)

gravel injection
grout injection

Derived termsedit

injection lipolysis
injection moulding

(construction) Terms derived from injection

injection cock
injection condenser
injection pipe

Translationsedit

act of injecting, or something injected

Armenian: ներարկում (hy) (nerarkum), սրսկում (hy) (srskum)
Asturian: f
Bulgarian: инжекция (bg) f (inžekcija)
Catalan: (ca) f
Chinese:

Mandarin: (zh) (zhùshè)
Dutch: (nl) f
Esperanto:
Finnish: ruiskutus (fi), (fi) (act), , (thing injected)
French: (fr) f
Galician: (gl) f
German: (de) f
Greek: (el) f (énesi)
Icelandic: innspýting (is) f
Ido: (io), (io)

Indonesian: (id), (id)
Japanese: (ja) (ちゅうしゃ, chūsha)
Korean: (ko) (jusa) ( (ko))
Malay: penyuntikan
Occitan: f
Polish: (pl) m, wstrzyknięcie (pl) n
Portuguese: (pt) f (Brazil), (pt) f (Portugal)
Romanian: (ro) f
Russian: (ru) f (inʺjékcija), (ru) m (ukól), (ru) n (vlivánije), впры́скивание (ru) n (vprýskivanije)
Serbo-Croatian:

Cyrillic: f, инјектирање n, убризгавање n

Roman: (sh) f, injektiranje n, ubrizgavanje n
Slovak: injekcia, vstreknutie, vstrekovanie
Swahili: (sw)
Walloon: pikeure (wa) f

medicine: something injected

Armenian: ներարկում (hy) (nerarkum), սրսկում (hy) (srskum)
Asturian: f
Catalan: (ca) f
Dutch: (nl), (nl)
Finnish: , (fi)
French: (fr) f
Galician: (gl) f
Georgian: (inekcia)
Greek:

Ancient: n (énema)
Hebrew: ‎ (he) f
Hungarian: (hu)
Indonesian: (id)
Italian: (it) f
Malay:

Malayalam: കുത്തിവെയ്പു് (kuttiveypŭŭ) ഇൻഞ്ചക്ഷൻ (inñcakṣan)
Occitan: f
Persian: تزریق‎ (fa) (tazriq), انژکسیون‎ (fa) (anžeksiyon)
Polish: (pl) m
Portuguese: (pt) f
Romanian: (ro) f
Russian: (ru) f (inʺjékcija)
Serbo-Croatian:

Cyrillic: f

Roman: (sh) f
Slovak: injekcia
Spanish: (es) f
Walloon: pikeure (wa) f

set theory: one-to-one mapping

Czech: (cs) f
Finnish: (fi)
French: (fr) f
German: (de) f
Greek: (el) f (emfýtefsi)
Japanese: 単射 (ja) (tansha)
Korean: 단사 (ko) (dansa) (單射)

Polish: (pl) f
Portuguese: f
Russian: (ru) f (inʺjékcija)
Serbo-Croatian:

Cyrillic: f

Roman: (sh) f
Slovak: injekcia
Swedish: (sv) c

computing: insertion of code

Bulgarian: вмъкване (bg) n (vmǎkvane)
Finnish: (fi)
French: please add this translation if you can
German: please add this translation if you can
Greek: please add this translation if you can
Spanish: please add this translation if you can

surjection (2)

injection on Wikipedia.Wikipedia

Lifetime and registration options

To demonstrate the difference between the lifetime and registration options, consider the following interfaces that represent tasks as an operation with a unique identifier, . Depending on how the lifetime of an operations service is configured for the following interfaces, the container provides either the same or a different instance of the service when requested by a class:

The interfaces are implemented in the class. The constructor generates a GUID if one isn’t supplied:

An is registered that depends on each of the other types. When is requested via dependency injection, it receives either a new instance of each service or an existing instance based on the lifetime of the dependent service.

When transient services are created when requested from the container, the of the service is different than the of the . receives a new instance of the class. The new instance yields a different .
When scoped services are created per client request, the of the service is the same as that of within a client request. Across client requests, both services share a different value.
When singleton and singleton-instance services are created once and used across all client requests and all services, the is constant across all service requests.

In , each type is added to the container according to its named lifetime:

The service is using a specific instance with a known ID of . It’s clear when this type is in use (its GUID is all zeroes).

The sample app demonstrates object lifetimes within and between individual requests. The sample app’s requests each kind of type and the . The page then displays all of the page model class’s and service’s values through property assignments:

Two following output shows the results of two requests:

First request:

Controller operations:

Transient: d233e165-f417-469b-a866-1cf1935d2518
Scoped: 5d997e2d-55f5-4a64-8388-51c4e3a1ad19
Singleton: 01271bc1-9e31-48e7-8f7c-7261b040ded9
Instance: 00000000-0000-0000-0000-000000000000

operations:

Transient: c6b049eb-1318-4e31-90f1-eb2dd849ff64
Scoped: 5d997e2d-55f5-4a64-8388-51c4e3a1ad19
Singleton: 01271bc1-9e31-48e7-8f7c-7261b040ded9
Instance: 00000000-0000-0000-0000-000000000000

Second request: