-
Notifications
You must be signed in to change notification settings - Fork 820
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.
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
Clarify parsing with offset using default moment function #300
Comments
Hi, I want to contribute to momentjs but i'm confused as there are 2 projects on Github for momentjs -https://github.com/moment/moment and https://github.com/moment/momentjs.com. Which one is the right one? Are both the same? Can someone help me on this please? I have currently cloned https://github.com/moment/momentjs.com |
moment is the source code, and momentjs.com is the documentation repository. |
Hi Maggie, thanks! Just one more clarification, will the momentjs.com repository contain only issues related to documentation? And not code related issues ? |
Hi. I'm a beginner to OSS contributions, and I'd like to contribute to moment.js. I've been looking at the Up-For-Grabs tag and notice that all the existing open issues are a couple years old. Is this issue still open and worth working on? Is there a new tag for beginner-friendly issues? |
This is listed https://momentjs.com/docs/#/parsing/ |
See stack overflow question:
http://stackoverflow.com/questions/37057907/meaning-of-z-in-format-string-in-moment-js#37058413
The default moment function will ALWAYS display in user's local time, regardless of offset parsed, unless .utc() is called on it. It will convert from specified offset to user's local time for display.
The text was updated successfully, but these errors were encountered: