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 are naming conflicts with native js classes such as Date so some of our classes are currently prefixed with _ e.g. _Date.
Since we plan to refactor our modules a bit and introduce string and number modules respectively we would like to decide on our naming strategy for the faker module classes to avoid these issues.
The classes will then be publicly exported with that name.
How should we name our modules (address, number, string, vehicle, helpers, ...
Xyz on conflicts with native classes _Xyz (e.g. _Date)
0%
XyzModule, they are modules so call them that
83%
XyzFaker, they are fakers specifically for Xyz
16%
FakerXyz, they are easier to find with autocompletion this way
s: needs decisionNeeds team/maintainer decisionc: refactorPR that affects the runtime behavior, but doesn't add new features or fixes bugs
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently there are naming conflicts with native js classes such as Date so some of our classes are currently prefixed with
_
e.g._Date
.Since we plan to refactor our modules a bit and introduce string and number modules respectively we would like to decide on our naming strategy for the faker module classes to avoid these issues.
The classes will then be publicly exported with that name.
6 votes ·
Beta Was this translation helpful? Give feedback.
All reactions