About FontAwesome PRO, "OriginHeaderDoesNotMatchKey" POST Error, Internationalization

[eTiTan]

I'm working on the code, trying to raise a server, i find some of challenges:

• FontAwesome PRO: i changed all PRO icons temporaly for the FREE version (i never do a pull request about it)
• OriginHeaderDoesNotMatchKey Error: on https://github.com/Bungie-net/api/issues/774 find the solution.
• i'm Native Spanish speaker

Propostals:

• FontAwesome PRO: Migrate to Iconify Angular Component, i want top help on it.
• OriginHeaderDoesNotMatchKey: Add a * on "Origin Header" on the Bungie.net App Config
• I can Help with Internationalization and Spanish Translation.

I want to discuss here for all because should be a short responses, i think that "OK", "THANKS", "NICE" maybe all the responses.

Regards.

[dcaslin]

Hi. Are you running at "https://localhost:4200" in dev mode? That's what you need to have the test D2Checklist api key match the origin header.

[eTiTan]

Yeah, i'm running "https://localhost:4200" at dev mode, i think that this is not a priority, i'm focus on replace the Font awesome pro icons, giving others chance to contribute too, and implement the internationalisation too.

i have a question, i want to known your opiinion, because i thinking how to do about the gliph that should to change (talking about Font Awesome Pro removal), i find that you are using a custon font set for some of gliph, i think that is a good idea.

Wath should be the "right" practice on this case?

Use a custom set (i can move/export/create) the needed gliph or use other font set like iconofy...

I need your opinion about it.

Regards.

[dcaslin]

I'm pretty heavily invested in FontAwesome Pro at this point. Not really looking to change it.