Steve Yin

Well, I've seen you guys work fast, as to this cache model, why don't we switch to `System.Runtime.Caching`? It provide a `MemoryCache` as pre made cache provider. so by using...

I know that, maybe I didn't make my self clear, I mean if we can switch to `System.Runtime.Caching`, and use `MemoryCache` to replace current memory model, then you don't need...

And this is exactly the same you changed from `log4net` to `Microsoft.Extensions.Logging`, right? by using `Microsoft.Extensions.Logging`, you only need to care about what to log, and leave how to log...

I doubt this project is abandoned now. At least is not actively maintaining. And this esent thing finally drives me away from this project. Because I need cross platform.

Thanks for the quick response, but your suggestion will not work, in version 6.2, every solid icon has a sharp version, so there is no any information in the `icons.json`....

and also, every solid sharp version has a `normal rounded solid` version, the two version seems equivalent. you can also checkout the changelog of version 6.2 here: https://fontawesome.com/docs/changelog/

in order to the this sharp solid version, you might also need to check if this is a pro version later than 6.2.0, in previous 6.x version, there is no...

here is the font-families.json icon example: ``` { "0": { "changes": [ "6.0.0-beta1", "6.2.0" ], "ligatures": [], "unicode": "30", "label": "0", "voted": false, "svgs": { "classic": { "solid": { "lastModified":...

Almost 2 years , any updates or roadmap of this? We also need hardware instancing function. I think this should be a standard feature.

well, how about this kind of design? I have padding under `ng-select`, the `.ng-container` is in side the padding. current design only opens when clicking the container, but is has...