Skip to content

Version 0.5.3 #293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 8, 2016
Merged

Version 0.5.3 #293

merged 1 commit into from
Sep 8, 2016

Conversation

samtstern
Copy link
Contributor

Bump to Version 0.5.3 and improve testing

Found out why Robolectric was not loading our resources (string-array vs array) so changed the test to now use the real resource loading code, which would have caught #290 and will prevent any regressions there.

Change-Id: Iaafad0f3b8707e862db6b7210bc2398e63d83396
@samtstern
Copy link
Contributor Author

@puf PTAL

@puf
Copy link
Contributor

puf commented Sep 8, 2016

lgtm on a code level. So I'm fine including this in 0.5.3.

I don't like the approach though. In general I prefer seeing these things in code, where they are more discoverable and can be made to auto-complete (I'm not sure if that applies to scopes specifically, since those are inherently stringly typed).

@samtstern samtstern merged commit a95d541 into firebase:master Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants