In my opinion, it is a bit harsh to throw an exception when booting the addon for a missing token to the Font Awesome API or a Font Awesome Kit. If so, this exception should only be thrown during development and only when the Font Awesome tag is used in a template. Otherwise, an info warning should be recorded in the log and simply no Font Awesome icon should be output.
aerni
commented
2 years ago
In my opinion, it is a bit harsh to throw an exception when booting the addon for a missing token to the Font Awesome API or a Font Awesome Kit. If so, this exception should only be thrown during development and only when the Font Awesome tag is used in a template. Otherwise, an info warning should be recorded in the log and simply no Font Awesome icon should be output.