You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no standard on entity holiday class naming. In general it somehow aligns with a country name. The idea is to use unified approach on entity class naming. For iso3166 entities it could be based either on alpha-2 or alpha-3 code, e.g. UsHolidays or UsaHolidays. The classes should still be available via their alpha-2 (and probably alpha-3) code aliases so for example US() and USA() imports would also work.
The text was updated successfully, but these errors were encountered:
Currently there is no standard on entity holiday class naming. In general it somehow aligns with a country name. The idea is to use unified approach on entity class naming. For iso3166 entities it could be based either on alpha-2 or alpha-3 code, e.g.
UsHolidays
orUsaHolidays
. The classes should still be available via their alpha-2 (and probably alpha-3) code aliases so for exampleUS()
andUSA()
imports would also work.The text was updated successfully, but these errors were encountered: