It is a security best practice to never commit a secret, especially within a publicly viewable repository. However, the following file has been committed to your repo:

• PowerBI-visuals-FacetKey/certs/PowerBICustomVisualTest_private.key

To resolve this issue, either revoke this key and remove it from the repo, OR add a comment indicating both why it is necessary to have this private key and why it is not a security risk.

Feature Request #2:
The "Range Value" feature is the best thing I have seen in a BI tool! Right now, its just shows a blue bar of different ranges. Could we have an option where, when the mouse is hovered over a binned range, it shows us the underlying Values too in a Tool Tip format?

Same could work for Segmented data as well.

Also, on the "Count" property, a Tooltip could show Column name of what is being Counted (or summed). After a while we tend to forget or even new users would not know what the count is for. A tooltip on mouse hover can show them the info.

Use the legacy version of package.json file for packaging when visual is using legacy api.

It looks like Facet Key works when used for developing locally on Power BI Desktop. As soon as it gets published online, it seems to stop working.
Power BI Desktop - no filter selected

Power BI Desktop - filter selected (works!)

Power BI online - no filter selected

Power BI online - filter selected (doesn't work)

This seems to be a regression from an older version.

Feature Request:
Finally, could we have an option to hide the Search Box? Sometime I have less than 5 items in the FacetKey, in such case we would not need a Search box :)

This also makes space for more Range

(While you are at it, may be allow us to hide borders as well :)
It looks great, but often I am forced to align my other visuals with it to make it look consistent :D )

Range facets are still blue (highlighted) when they are collapsed

Feature Request #1:
Option to set font size for Headers, Facet. At full screen, the Facet fonts look really big somethings and this this limits the number of values shown too.

Would be great if we could control the fonts for "Count" and Range too (but not necessary). It could be same as Facet font size.

(Submitting feature requesting as requested by @jryu01 )

Feature Request:
Use of Font Awesome icon is a GREAT feature!
However right now it always depends on a Column to populate its icon. Can there be a way where I enter a FA icon name directly into the property window? This would eliminate the necessity to have a special column designated only for this purpose.

(More explanation from my comments)

its not really a high priority request, but I will tell you from where I am coming. I am primarily using the FacetKey visual as Slicer, due to the fact that it allows me to Search, Select, segment, filter, and even have metrics (like count, sum of another field!!) These are amazing features to have in a Slicer. It changes the way my user filter their data. The icon feature I requested could be similar to assigning a "Background color" or Font size. Alternate to assigning a Column (with FA icon name), if I could also specify my own text, it would remove the need to create a "icon" column only for this purpose.

We have Range Values added on top of the FacetKeys. Now when I click the "more" option for a FacetKey, it just expands the Visual to the end of the screen (even if there is another visual below). Then the whole visual gets a scrollbar.

If somehow, the scrollbar could be limited to the respective Facet only, then it would have other filters fixed at the set height.

When I slide the two handles, the upper range text disappears on all Ranges. This doesn't get Reset until you resize the FacetKey Visual.
(Confirmed as known bug by @darionco, fix already scheduled. Adding here as requested)

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.