This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Changing processing order, ancestors first#424
Merged
pyricau merged 1 commit intoDec 6, 2012
developandroidannotations/androidannotations:developfrom
296_call_orderandroidannotations/androidannotations:296_call_orderCopy head branch name to clipboard
Merged
Changing processing order, ancestors first#424pyricau merged 1 commit intodevelopandroidannotations/androidannotations:developfrom 296_call_orderandroidannotations/androidannotations:296_call_orderCopy head branch name to clipboard
pyricau merged 1 commit into
developandroidannotations/androidannotations:developfrom
296_call_orderandroidannotations/androidannotations:296_call_orderCopy head branch name to clipboard
Conversation
pyricau
added a commit
that referenced
this pull request
Dec 6, 2012
Changing processing order, ancestors first. Fixes #296
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #296
We are now processing the ancestors elements first, so that
@AfterInjectand@AfterViewsin parent classes are called first.