Closed vladikoff closed 8 years ago
Hm seems like it won't work for most cases
I think the point is that options.keyword
is actually an array, not a string. Have you tried supplying an array with your custom string? E.g. ["translator.gettext"]
.
+1 to what @maufl says.
Thank you all for a quick response, we've been using that option as a string for a very long time and I guess it got lost somewhere in history. 👍
@BYK @zaach Could you check this?
given
"translator.gettext".indexOf("get")
will skip the statement and add the keyword into parsed strings?