Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Improve Initial FontAwesome Config; Free vs. Pro #89

Open
jeremy-farrance opened this issue Dec 7, 2019 · 0 comments
Open

Improve Initial FontAwesome Config; Free vs. Pro #89

jeremy-farrance opened this issue Dec 7, 2019 · 0 comments

Comments

@jeremy-farrance
Copy link
Collaborator

jeremy-farrance commented Dec 7, 2019

We already have a switch to enable FontAwesome usage. Since the pattern is so specific, it would be nice to also have a switch that specifies fa Free vs. Pro and gets the right thing in place for each.

Maybe even ... although the Pro isTrue might be unneeded, just including the KITID should be enough to switch and use that pattern.

vendors: {
    bootstrap: isTrue(VENDOR_BOOTSTRAP),
    flickity: isTrue(VENDOR_FLICKITY),
    fontAwesome: isTrue(VENDOR_FONT_AWESOME),
    fontAwesomePro: isTrue(VENDOR_FA_PRO),
    fontAwesomeKitId: VENDOR_FA_KITID
  },
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant