Skip to content

Conversation

lsmith77
Copy link
Member

@lsmith77 lsmith77 commented Oct 3, 2014

attempt to fix #557

but how to test this?

@lsmith77
Copy link
Member Author

lsmith77 commented Oct 3, 2014

cc @dbu

@dbu
Copy link
Member

dbu commented Oct 6, 2014

seems correct to me.

to test, you would load a document, change a field, do a loadTranslation and check that the field was not reset.

and i would add a note to the changelog as its a bugfix with a potential to break something if it relied on this.

@lsmith77 lsmith77 force-pushed the make_findTranslation_consistent branch from 994dbaa to e917f7c Compare October 6, 2014 12:45
Copy link
Member Author

Choose a reason for hiding this comment

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

we were clearing the loaded translations on flush, which I guess was a memory optimization but caused the translations to be loaded again either way.

@lsmith77
Copy link
Member Author

lsmith77 commented Oct 6, 2014

@dbu can you review and merge?

@dbu
Copy link
Member

dbu commented Oct 6, 2014

what about a note in the changelog?

@lsmith77 lsmith77 force-pushed the make_findTranslation_consistent branch from e917f7c to 434849c Compare October 6, 2014 14:49
@lsmith77
Copy link
Member Author

lsmith77 commented Oct 6, 2014

added

@lsmith77 lsmith77 force-pushed the make_findTranslation_consistent branch from 434849c to a3ec655 Compare October 6, 2014 14:50
dbu added a commit that referenced this pull request Oct 6, 2014
no longer refresh translations on a load translation call
@dbu dbu merged commit c8e2d13 into master Oct 6, 2014
@dbu dbu deleted the make_findTranslation_consistent branch October 6, 2014 16:31
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.

make findTranslation consistent to find
2 participants