Feature request: default size

[Waterstraal]

Describe the problem you'd like to see solved or task you'd like to see made easier

Currently you can set a defaultPrefix and fixedWidth in FaConfig:

export class AppModule {
  constructor(faConfig: FaConfig) {
    faConfig.fixedWidth = true;
    faConfig.defaultPrefix = 'far';
  }
}

I would like to set a default size as well, so that I don't have to specify it for each individual icon.
I can also imagine that it would be nice to be able to set a default for each existing fa-icon property.

Is this in relation to an existing part of angular-fontawesome or something new?

Yes, FaConfig

What is 1 thing that we can do when building this feature that will guarantee that it is awesome?

Extend FaConfig with a defaultSize property, and possibly with all the other fa-icon properties as well.

Why would other angular-fontawesome users care about this?

It would make them more efficient & their codebase cleaner.

On a scale of 1 (sometime in the future) to 10 (absolutely right now), how soon would you recommend we make this feature?

10

Feature request checklist

• This is a single feature (i.e. not a re-write of all of Font Awesome)
• The title starts with "Feature request: " and is followed by a clear feature name (Ex: Feature request: moar cowbell)
• I have searched for existing issues and to the best of my knowledge this is not a duplicate

[devoto13]

By default, the icon should match the font size of the place where it is added. I wonder why you need to change it? Can you describe your use case in more detail?

Extend FaConfig with a defaultSize property, and possibly with all the other fa-icon properties as well.

I think it is better to evaluate default properties case by case and decide if we want to implement them. The size is present in multiple components, I wonder if we should implement defaults per-component, single flag for all, or both. Per-component defaults should also be useful for #295.

[Waterstraal]

Can you describe your use case in more detail?

I like the "lg" size (top) better than the default size (bottom):

I think it is better to evaluate default properties case by case and decide if we want to implement them. The size is present in multiple components, I wonder if we should implement defaults per-component, single flag for all, or both. Per-component defaults should also be useful for #295.

I think it makes sense to support a hierarchy of defaults where the lowest defined prop takes precedence: root > per component type > individual component