8000 New @Receiver attribute: scheme #1096 by dodgex · Pull Request #1101 · androidannotations/androidannotations · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Feb 26, 2023. It is now read-only.

Conversation

@dodgex
Copy link
Member
@dodgex dodgex commented Aug 22, 2014

this implements: #1096

@WonderCsabo
Copy link
Member

Thanks! @yDelouis please review the code, as the original author of @Receiver.
However, i have the same note again: where is the test?

@dodgex
Copy link
Member Author
dodgex commented Aug 22, 2014

i'm just working on the tests. same as in @ReceiverAction, there are classes with this annotation in functional-test-1-5 but no actual tests in functional-test-1-5-tests

@dodgex
Copy link
Member Author
dodgex commented Aug 22, 2014

interesting. not sure if it is a robolectric problem, but if i have dataSchemes = "http" the receiver also receives Intents with e.g. ftp as dataScheme in the test :(

@WonderCsabo
Copy link
Member

Can you post your tests? If you are still not certain about rebasing, just simply create a branch without a pull request.

@dodgex
Copy link
Member Author
dodgex commented Aug 22, 2014

https://github.com/dodgex/androidannotations/tree/ReceiverDataSchemesTest onDataShemeHttpTest fails on line 55 (assertFalse) as the receiver gets the Intent even if it shouldnt :(

@WonderCsabo
Copy link
Member

I tested and i think you are right. Can you create a simple test-case project (for example based on deckard) so we can ask about this issue in the robolectric GitHub page?

@dodgex
Copy link
Member Author
dodgex commented Aug 23, 2014

i have openend an issue on robolectric with sample project. robolectric/robolectric#1244

@WonderCsabo
Copy link
Member

Thank you! I hope we get some response from the robolectric team soon.

@WonderCsabo
Copy link
Member

@dodgex next time please include the issue number in the branch name, like it is described here.

@dodgex
Copy link
Member Author
dodgex commented Aug 25, 2014

@WonderCsabo okay. sorry.

@WonderCsabo
Copy link
Member

It seems we won't have a response from the robolectric team soon. Please add your tests to this PR, and comment @Test for the falsely failing tests.

@dodgex
Copy link
Member Author
dodgex commented Aug 27, 2014

done with a comment why the test is commented out and a link to the robolectric issue

@dodgex
Copy link
Member Author
dodgex commented Aug 27, 2014

i also proposed a PR(robolectric/robolectric#1250) to robolectric fixing the tests. so a response is (hopefully) more likely

@WonderCsabo
Copy link
Member

Nice and easy fix! But i think you also have to add some tests here.

However, your change will not be available soon in a stable robolectric release, so we should leave the test commented for now.

8000
@dodgex
Copy link
Member Author
dodgex commented Aug 28, 2014

@WonderCsabo you are right. ;)

Jake asked me to add tests. have done that now. :)

@dodgex
Copy link
Member Author
dodgex commented Aug 28, 2014

The PR is merged. So as soon as 2.4 gets released we can enable our test. 👍

@WonderCsabo
Copy link
Member

Congrats, and thanks! It seems they are only react to PRs... I did not get any responses in this issue (also related to AA), despite i also posted about in the robolectric mailing list.

@dodgex
Copy link
Member Author
dodgex commented Aug 28, 2014

Congrats, and thanks!

AA saved me so much time and made my code cleaner. I want to give something back. not only by implementing stuff i need, but also by implementing stuff that others could need. like this one.

I'm proud to be able to contribute! :)

@WonderCsabo
Copy link
Member

@yDelouis do you plan to review this?

@dodgex
Copy link
Member Author
dodgex commented Sep 20, 2014

rebased on current develop.

yDelouis added a commit that referenced this pull request Sep 21, 2014
@yDelouis yDelouis merged commit dae02a3 into androidannotations:develop Sep 21, 2014
@yDelouis
Copy link
Contributor

Good work ! Thanks.
There is only one typo that I will fix.

@yDelouis yDelouis added this to the 3.2 milestone Sep 21, 2014
@WonderCsabo
67E6 Copy link
Member

@dodgex Please add documentation. Before that, reset your wiki to our HEAD, because i rebased your commits. Also please be careful about line endings. Thanks.

@WonderCsabo
Copy link
Member

Also the JavaDoc is missing for this feature. Please add that in a new PR.

@dodgex
Copy link
Member Author
dodgex commented Sep 21, 2014

WTH. I'm 100% sure there was javadoc. might be lost during the rebase as the import in the EReceiver PR.

I'll try to fix this asap. same for wiki.

@dodgex dodgex deleted the ReceiverDataSchemes branch September 21, 2014 14:38
@dodgex dodgex restored the ReceiverDataSchemes branch September 21, 2014 14:42
@dodgex dodgex mentioned this pull request Sep 21, 2014
@dodgex
Copy link
Member Author
dodgex commented Sep 21, 2014

already posted link to wiki update in PR but to have it in the issue with "WikiUpdate" label i'll post it here too

https://github.com/dodgex/androidannotations/wiki/Receiving-intents

@WonderCsabo
Copy link
Member

Wiki updated, thanks!

@dodgex dodgex deleted the ReceiverDataSchemes branch September 22, 2014 06:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

0