Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explain why "ISO" and "UTC" are not in capitals in function names #80

Open
bjuppa opened this issue Aug 10, 2023 · 0 comments
Open

Explain why "ISO" and "UTC" are not in capitals in function names #80

bjuppa opened this issue Aug 10, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@bjuppa
Copy link
Owner

bjuppa commented Aug 10, 2023 •
edited
Loading

This could go among the guiding principles in docs. It's because I think abbreviations in caps makes the function name harder to read when mixed between two other words. And our interfaces only have toJSON that has only one word!

Also explain that Date's toISOString is rarely used in userland code so would just bloat the ComPlainDate objects that already have the iso property.
@bjuppa bjuppa added the documentation Improvements or additions to documentation label Aug 10, 2023
@bjuppa bjuppa changed the title Explain why not ISO and UTC in capitals in function names Explain why "ISO" and "UTC" are not in capitals in function names Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bjuppa