I am trying to format a date type property on a model before displaying it. This is the code that I am using:
// MODEL
var mongoose = require('mongoose'),
Schema = mongoose.Schema;
var ArticleSchema = new Schema({
title: String,
content: String,
author: { type: String, default: 'Vlad'},
postDate: { type: Date, default: Date.now }
});
ArticleSchema.methods.formatTitle = function() {
var link = this.title.replace(/\s/g, '-');
return '/article/' + link;
};
ArticleSchema.methods.snapshot = function() {
var snapshot = this.content.substring(0, 500);
return snapshot;
};
ArticleSchema.methods.dateString = function() {
var date = new Date(this.postDate);
return date.toDateString();
};
module.exports = mongoose.model('Article', ArticleSchema);
And on the client side I try to display the formatted date using:
{{ article.dateString }}
Still, whenever I load a view that contains this element, I get a 500 error:
Cannot call method 'toDateString' of undefined
EDIT1: I have no issue embedding {{ article.snapshot }} in my Views, but when it comes to the Date object, I get an error
EDIT2: When logging the dateString method using console.log(article.dateString()) I get the following:
Wed Sep 18 2013
EDIT3: This is when I get when using the code provided by dankohn. Is it just me, or is it simply running the method two times in a row?
this.postdate: Wed Sep 18 2013 23:27:02 GMT+0300 (EEST)
parsed: 1379536022000
date: Wed Sep 18 2013 23:27:02 GMT+0300 (EEST)
toString: Wed Sep 18 2013
Wed Sep 18 2013
this.postdate: undefined
parsed: NaN
date: Invalid Date
toString: Invalid Date
I've rewritten this to make perfectly clear where your date stuff is failing:
ArticleSchema.methods.dateString =
console.log('this.PostDate: ' + this.postDate)
var parsed = Date.parse(this.postDate)
console.log('parsed: ' + parsed)
var date = new Date(parsed);
console.log('date: ' + date)
var toString = date.toDateString();
comsole.log('toString: ' + toString)
return toString;
};
Separately, if this doesn't work for you, I recommend the library moment, which is much easier to work with than native Javascript dates.
Related
The Dates on my NodeJS Side are Correct.
Once The User receives the event (On Their Email Client) the dates are Incorrect.
The Dates are always off by an Exact amount
-1 On the Starting Day E.G 02 Feb -> 01 Feb.
-2 On the Ending Date E.G 05Feb -> 03Feb
Dates are Received from an Angular Application, I can confirm the dates provided are correct dates Formatting is another matter.
Is my Formatting Incorrect? & or Is this a TimeZone Problem?
Please find Below Code:
I am Unsure How to Recreate a working Example of a Node.js Application
using the SO builder, Please Lend guidance regarding this if required and I will update were needed
var startDate = new Date(user.sDate)//YYYY/MM/DD;
var EndDate = new Date(user.eDate)//YYYY/MM/DD
var builder = icalToolkit.createIcsFileBuilder();
builder.calname = 'Temp Cal';
builder.timezone = 'Africa/Johannesburg';
builder.tzid = 'Africa/Johannesburg';
builder.method = 'REQUEST';
console.log(startDate + " sDate") //Sat Feb 25 2023 00:00:00 GMT+0200 (South Africa Standard Time)
console.log(user.eDate + " eDate") //2023/02/27 eDate
builder.events.push({
//Required: type Date()
start: startDate,
end: EndDate,
summary: 'Test Event',
allDay: true,
description: 'Testing it!',
organizer: {
name: 'SomePlace ',
email: 'someemail#mail.com',
sentBy: 'someemail#mail.com'
},
method: 'REQUEST',
status: 'CONFIRMED',
})
var icsFileContent = builder.toString();
let mailOptions = {
from: 'emailsending#mail.com', // sender address
to: "whicheveremail#mail.com", // list of receivers
subject: "New Booking Made", // Subject line
html: `<h1>Hi ${user.name}</h1><br>
<h4>Here is your new Booking</h4><br>
<p>Calendar Event Here: </p>
<p>${user.sDate}</p><br>
<p>${user.eDate}</p><br>`,
alternatives: [{
contentType: 'text/calendar; charset="utf-8"; method=REQUEST',
content: icsFileContent.toString()
}]
};
let info = await transporter.sendMail(mailOptions);
callback(info);
Extra info:
Angular App Date Formatting:
const format = 'yyyy/MM/dd';
const startD = sy+ "-" + sm + "-" + sd;
const endD = ey+ "-" + em + "-" + ed;
const locale = 'en-US';
const formattedDateStart = formatDate(startD, format, locale);
const formattedDateEnd = formatDate(endD, format, locale);
this.SendEmail(formattedDateStart,formattedDateEnd);
I'm trying to validate some input with hapijs/joi and joi-date-extensions
. I write this code example1.js:
const BaseJoi = require('joi');
const Extension = require('joi-date-extensions');
const Joi = BaseJoi.extend(Extension);
const schema = Joi.object().keys({
start_date: Joi.date().format('YYYY-MM-DD').raw(),
end_date: Joi.date().min(Joi.ref('start_date')).format('YYYY-MM-DD').raw(),
});
const obj = {
start_date: '2018-07-01',
end_date: '2018-06-30',
}
console.log(schema.validate(obj));
the code returns this error:
child "end_date" fails because ["end_date" must be larger than or equal to "Sun Jul 01 2018 01:00:00 GMT+0100 (CET)"]
However I want to get the original input in the error, somthing like that:
child "end_date" fails because ["end_date" must be larger than or equal to "2018-07-01"]
When I tried this instruction in the example2.js:
start_date = Joi.date().format('YYYY-MM-DD');
console.log(start_date.validate('2018-07-31'));
The result was:
Tue Jul 31 2018 00:00:00 GMT+0100 (CET)
when I use the raw() in the example3.js:
start_date = Joi.date().format('YYYY-MM-DD').raw();
console.log(start_date.validate('2018-07-31'));
it returns:
"2018-07-31"
In the example1.js I want to get the original date entred by my code. How can I fix that?
.raw controls how data is transmitted to Joi.validate's callback, i.e. what your data looks like after the validation process. It does not control what happens on errors.
To do that, you may want to use .error. I never used it but I guess it'd be something like this:
Joi.date().min(Joi.ref('start_date')).format('YYYY-MM-DD').raw().error(function (errors) {
var out = [];
errors.forEach(function (e) {
out.push(e.message.replace(/".*?"/g, function(match) {
var dateMatch = Date.parse(match);
if (isNaN(dateMatch)) {
return match;
} else {
// return formatted date from `dateMatch` here, too lazy to write it in p[l]ain JS...
}
}));
});
return out;
})
I am new to node and I was going through Date() object, values and Date format in Node. When I run the below code, I get different output in console.
const date_1 = new Date();
console.log(date_1);
const date_2 = new Date();
console.log(+date_2);
const date_3 = new Date();
console.log('comma:',date_3);
const date_4 = new Date();
console.log('plus:'+date_4);
gives the below output in console?
2018-02-01T06:55:41.327Z
1517468141327
comma: 2018-02-01T06:55:41.327Z
plus:Thu Feb 01 2018 12:25:41 GMT+0530 (India Standard Time)
Can someone let me know what I am missing here in terms of understanding.
For the first and third case are displayed as default
new Date().toJSON()
For second case +new Date() unary operator, it's equivalent to:
function(){ return Number(new Date); }
For the fourth case 'plus:'+date_4, the string are concatenated as result the date is equivalent to
'plus:'+date_4.toString()
The value of new Date() is the universal format(Z) so when you log a date, It's value is logged.
console.log(date);
console.log('abc',date);
But when + operator with a number of just + is used it converts it to Number format(milliseconds in case of date) -
console.log(+date);
console.log(1+'a'); // NaN
And when you use + with a string, It gets toString() value of date which is Thu Feb 01 2018 12:45:21 GMT+0530 (IST)
console.log(date.toString()); // Thu Feb 01 2018 12:45:21 GMT+0530 (IST)
You are implicitly converting your date to something else:
const date_1 = new Date();
console.log(date_1); //prints date as a Date object
const date_2 = new Date();
console.log(+date_2); //converts date to a number
const date_3 = new Date();
console.log('comma:',date_3); //prints date as a Date object
const date_4 = new Date();
console.log('plus:'+date_4); //converts date to a String
Mongoose is saving date-time as ISODate("2017-04-25T09:40:48.193Z")in UTC format. How can i change its time zone to my local server timezone. So i need not to change the time every time i retrieve it from db. Here is my model schema:
var MyModelSchema = new mongoose.Schema(
{
id: Number,
description: String,
created: {type: Date},
modified: {type: Date, default: Date.now},
},
{
collection: 'my'
}
);
PS: I am aware that it is preferred to save time in UTC format but here my requirement is to save it in specified time-zone.
you can save users timezone and while updating add the time zone value to this new object. Better to use moment.js to convert this.
moment
Even thought it is not a good practice to store time in local format but this might help -
date = new Date(); //2017-04-25T06:23:36.510Z
date.toLocaleTimeString(); //'11:53:36 AM'
localDate = ""+d; //'Tue Apr 25 2017 11:53:36 GMT+0530 (IST)'
changes will be done where you are saving the Object -
var date = new Date(); //2017-04-25T06:23:36.510Z
date.toLocaleTimeString(); //'11:53:36 AM'
var localDate = ""+d; //'Tue Apr 25 2017 11:53:36 GMT+0530 (IST)'
var newModel = new ModelSchema()
newModel.description = 'Something';
newModel.created = locaDate;
newModel.save(function(err) {
if (err)
throw err;
return done(null, newUser);
});
I think I have a solution. Try this one for Asia/Calcutta this can be stored as Date type in Mongoose
function getCurrentIndianDateTime(){
var moment = require('moment-timezone');
var time = moment.tz('Asia/Calcutta').format("YYYY-MM-DDTHH:MM:ss");
return new Date(time);
}
I'm writing a React Application that uses MongoDB as its database. There seems to be some strange behaviour when saving and retrieving dates from the database, specifically when updating the date in a particular document.
When I create a new document, everything is fine. However, if I try to edit the date on that document using an ajax call, the date stored in MongoDB is one day earlier than the one I selected and what is displayed in the browser. Code below to explain a little more.
The date is selected using an HTML5 <input type='date' /> element. Here's some of the code. I've included console logs at various points to show the output. Let's assume I'm selecting '30 October 2016' as the date. The date and the year get split up for display purposes elsewhere, but then joined together in the form of a JS Date object before sending to the server (see code below)
React component method:
saveChanges(e, cancel){
e.preventDefault();
const cancelled = cancel ? true : false
console.log(this.state.date); // 30 Oct
console.log(this.state.year); // 2016
const saveData = {
id: this.props.data.id,
venue: this.state.venue,
unitNumber: this.state.unitNumber,
unitName: this.state.unitName,
date: this.state.date,
year: this.state.year,
day: this.state.day,
tutorID: this.state.tutorID,
cancelled: cancelled
}
editWorkshop(saveData, (data) => {
this.props.getWorkshopDetails();
this.props.workshopDetailsSaved(data);
});
}
The above method sends the data to editWorkshop.js, an external ajax call, using axios:
import axios from 'axios';
export default function editWorkshop(input, callback){
const date = new Date(input.date + ' ' + input.year) // Rejoin date and year and convert to Date object
console.log(date); // Sun Oct 30 2016 00:00:00 GMT+0100 (BST)
const data = {
id: input.id,
venue: input.venue,
unitNumber: input.unitNumber,
unitName: input.unitName,
date: date,
day: input.day,
tutorID: input.tutorID,
cancelled: input.cancelled
}
axios.post('/editWorkshop', data).then(function(res){
callback(res.data);
})
}
And finally the express route which handles the ajax call
const express = require('express');
const Workshop = require('../data/models/Workshop');
module.exports = function(req, res){
const data = req.body
console.log(data.date); // 2016-10-29T23:00:00.000Z - here is where it seems to go wrong - notice that the date has changed to 2016-10-29 instead of 10-30. This now gets written to the database
Workshop.update({ _id: data.id }, {
$set: {
unitNumber: data.unitNumber,
date: data.date,
venue: data.venue,
tutor: data.tutorID,
session: data.day,
cancelled: data.cancelled
}
}, function(err){
if (err) {
res.send(err);
return
}
var message = 'Workshop updated'
res.send({
success: true,
message: message
});
})
}
What's really strange is that when I retrieve the data from the database elsewhere in the application, it shows the correct date in the browser - 30 Oct 2016.
Arguably this isn't a problem as the correct date is being displayed, but I'm not comfortable with this as these dates are a fundamental part of the app and I'm concerned that there could be scope for a bug in the future.
Can anyone shed any light on this?
2016-10-29T23:00:00.000Z is same as Sun Oct 30 2016 00:00:00 GMT+0100 (BST).
2016-10-29T23:00:00.000Z is in UTC(GMT) timezone. If you convert that to BST you will get the same value.
MongoDB saves the date values as UTC milliseconds since the Epoch.
From the docs:
MongoDB stores times in UTC by default, and will convert any local
time representations into this form. Applications that must operate or
report on some unmodified local time value may store the time zone
alongside the UTC timestamp, and compute the original local time in
their application logic.