Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

rely on content not content state when determine what can be omitted in push #58

Merged
merged 1 commit into from
Apr 23, 2015

Conversation

huangp
Copy link
Collaborator

@huangp huangp commented Apr 23, 2015

When dealing with plural entries, the content state is not always reliable.

return input == null
|| input.getContents().isEmpty()
|| all(input.getContents(),
blankStringPredicate);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about the input.getState().isUntranslated(); condition?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not reliable when dealing with plural entries. We treat it as untranslated if not all plurals have value. Therefore the original implementation will miss some partial translations

@alex-sl-eng
Copy link
Member

👍

@definite definite added Verified and removed On QA labels Apr 23, 2015
huangp pushed a commit that referenced this pull request Apr 23, 2015
rely on content not content state when determine what can be omitted in push
@huangp huangp merged commit 01b6542 into integration/master Apr 23, 2015
@huangp huangp deleted the fix-optimization-bug branch April 23, 2015 07:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants