I noticed that there was support for having an array of translation attributes for HTML tags, but not inside angular filters. So instead of using the initial single attribute in mkAttrRegex (that was previously hardcoded btw), it now uses the attributes array that can be specified as an option to the Extractor. This change is useful when having two different angular filters that both should be picked up and extracted for translation.
I noticed that there was support for having an array of translation attributes for HTML tags, but not inside angular filters. So instead of using the initial single
attribute
inmkAttrRegex
(that was previously hardcoded btw), it now uses theattributes
array that can be specified as an option to theExtractor
. This change is useful when having two different angular filters that both should be picked up and extracted for translation.