Don't change status `fuzzy` to `waiting` if translation has warnings #646

Closed
ocean90 opened this Issue Jan 29, 2017 · 0 comments

Projects

None yet

1 participant

@ocean90
Member
ocean90 commented Jan 29, 2017 edited

Originally introduced in #402.

Steps to reproduce:

  • Prepare a translation file that will produce a warning
  • Import translations via CLI and use the status argument with fuzzy (#591)

Expected: Translations with warnings still have the status fuzzy
Actual: Translations with warnings are set to waiting

@ocean90 ocean90 added the bug label Jan 29, 2017
@ocean90 ocean90 added this to the 2.3 milestone Jan 29, 2017
@toolstack toolstack closed this in #647 Jan 30, 2017
@ocean90 ocean90 self-assigned this Jan 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment