-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bugfix (value filter does not filter out all empty values) #16
Conversation
Additional content parsing is influenced by special page/template status. An eyeball check on the following options (format=tagcloud): 1 link=all 2 link=none 3 template=TagCloud / link=none 4 template=TagCloud / link=all 5 widget=wordcloud / link=none 6 widget=wordcloud / link=all 7 widget=wordcloud / template=TagCloud 8 widget=sphere / link=none 9 widget=sphere / link=all 10 widget=sphere / template=TagCloud
Added a case for empty values
I'm guessing it does what it says as we don't run any qunit tests here. |
bugfix (value filter does not filter out all empty values)
for ( var j = 0; j < printoutValues.length && ! selectedFoundInPrintout; ++j ) { | ||
selectedFoundInPrintout = selectedFoundInPrintout || ( printoutValues[j] == targetValues[k] ); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
such indenting. many complexly. much wow omg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quite true. Truth be told, the whole format could well use a rewrite.
@s7eph4n Can you please add a line about this in the release notes (for 1.9.1)? |
Sorry for not responding. Was on vacation without internet access. |
I already updated the stuff |
Added a case for empty values