'popScope' has different behaivior on develop / release build.

[swissonid]

I do not know if its intentional or not. The assertion gets removed/disabled during the release build. Which can lead to strange behaviour without any meaningful error message. Or just not to pop if you are on the baseScope

@override
  Future<void> popScope() async {
    assert(
        _scopes.length > 1,
        "You are already on the base scope. you can't pop"
        ' this one');
    await _currentScope.dispose();
    await _currentScope.reset(dispose: true);
    _scopes.removeLast();
  }

[escamoteur]

That is correct. But that's the idea of asserts in general. Do you see it as an error situation that could happen in release that wouldn't be a fatal error that should have been detected during development?

[swissonid]

I just run in one of that situation mention in issue #153. I was relying on the thrown exception not realising that is was thrown by an assertion. It took me a day to find the bug. Is there any reason why not just prevent to pop the baseScope anyway?

[escamoteur]

yes, IMHO if that happens something is wrong with your App, so it's better to have an assert.

[swissonid]

Ok, let's assume something is wrong in my app. Still would it not be nice if GetIt would prevent the User, in that case, the developer to make so silly mistake as I did? So that the end user gets a better experience. And print a warning or event throw an exception? So we get both, a happy end-user and GetIt can show to the developer he has done something properly wrong.

[escamoteur]

I'm a big fan of ailing fast :-) But I agree we could change this into an if with an exception instead of the assert, so that you get a meaningful error message

[escamoteur]

Implemented in V6.1.0