I remember old-timey app code having lots of `Build.VERSION` checks for
working around bugs and stuff, so it was useful to be able to manipulate it
discretely.

Maybe move the change to a different PR?

--X [typos courtesy of my iPhone]

On Dec 18, 2013, at 22:09, Erich Douglass <notifications@github.com> wrote:

In src/main/java/org/robolectric/annotation/Config.java:

> @@ -125,10 +114,6 @@ public Implementation(Config baseConfig, Config overlayConfig) {
>        return qualifiers;
>      }
>
> -    @Override public int reportSdk() {

Now that we load different SDKs at run time, it felt weird to report one
SDK level even though Robolectric might be running with a different set of
code. If I were a user, I might be somewhat confused about how the two
flags would interact. Maybe we should just set the SDK level to whatever
the user has specified and then try to load the SDK that's the closest
match? It could still lead to some strange test behavior, though.

—
Reply to this email directly or view it on
GitHub<https://github.com/robolectric/robolectric/pull/881/files#r8461460>
.