Skip to content
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

Bugfix for ERXSortOrder introduced by commit 65a54 #169

Closed
wants to merge 4 commits into from

Conversation

avendasora
Copy link
Member

Bugfix for 65a54e2. Also includes original code.

avendasora added 4 commits May 1, 2012 16:58
…Ordering and NSArray<EOSortOrdering> as well.
…ray<EOSortOrdering> to be synonyms for the prefix() methods. This overloading of #dot() makes prefixing existing EOQualifiers, EOSortOrdering and ERXSortOrderings much more intuitive. For example, let's say Company has a complex array of EOSortOrderings that takes into account things like outstanding invoice amounts, days past due, etc that is expressed in a static field called Company.FINANCIAL_SORT. With the dot() method you could easily create a new array of EOSortOrderings for the Invoice entity by simply writing: Invoice.COMPANY.dot(Company.FINANCIAL_SORT).then(Invoice.DUE_DATE). This allows each Entity to know about it's own EOSortOrderings and you don't have to have EOSortOrderings duplicated in every class (or component) that needs to do a sort.
…ings to the array, and on top of that it doesn't really work to update a mutable array that is then just regenerated without the changes.
@avendasora
Copy link
Member Author

Forget this, creating a new branch with just the bug fix. Will create a new pull request from there.

@avendasora avendasora closed this May 2, 2012
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.

1 participant