# GlobalScope

{% hint style="info" %}
GlobalScope is only available in the 2.3 beta, is experimental and likely to change.
{% endhint %}

A GlobalScope implements the Singleton pattern with improvements.

When you inject a value into a GlobalScope it is available to your entire application (including in flutter build methods).

A classic example of using a GlobalScope is to hold the currently logged in user.

```dart
final userKey = ScopeKey<User>();
final user = validateLogin(username, password);
if (user != null) {
    GlobalScope().value(userKey, user);
}
```

{% hint style="success" %}
We use `guse` rather than `use` to get global ScopeKeys.
{% endhint %}

Now that you have the user you can get them from anywhere in your code.

```dart
final user = use(userKey);
```

### An improved singleton

The problem with the Singleton pattern is that it doesn't play nicely when it comes to unit testing.

GlobalScope solves this problem by being aware of any Scope keys and allowing a Scope key to override a GlobalScope key.

```dart
void main() {
    GlobalScope().value(userKey, user);
}

test('a unit test', () {
    final user = use(userKey); // return user injected in main
    Scope().
    ..value(userKey, testUser) // override the userKey
    ..run(() => 
    {
        final user = use(userKey); // returns testUser
    });
    // we are back outside the Scope.
    final user = use(userKey); // return user injected in main
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://scope.onepub.dev/fundamentals/globalscope.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.