Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Move back to using real dates #4

Closed
possibilities opened this Issue · 7 comments

4 participants

@possibilities

No description provided.

@wizonesolutions

What does this mean?

@tmeasday
Owner

Oh; I think we store date as timestamps (something like date.intValue()), where as Meteor supports proper Date objects now.

@wizonesolutions

Which timestamps? Just wondering if it matters...mrt just wraps Meteor.

@tmeasday
Owner

The timestamps of the package created/update dates

@wizonesolutions

Ah. Does Meteor use those in its package system?

@Tarang
Collaborator

Yes at the moment the packages times are stored as the javascript unix timestamp value. If you check out atmosphere and use Packages.findOne() in your browser's javascript console the updatedAt and createdAt values are integers, but we could store them as Date objects instead.

It might be better to hold on for EJSON to be implemented in the node-ddp-client so we can easily use them in meteorite without having to do type conversion though. That is if meteorite uses these values somewhere, which im a bit unsure of.

@TomasDuda TomasDuda referenced this issue from a commit in TomasDuda/atmosphere
@TomasDuda TomasDuda Fix #47 (middle-clicking in Chrome)
Close #44 (GitHub star button)
Add a real date to span (see #4)
Always show the search input
4362722
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.