Dress to Impress, a big fancy Neopets customization tool!
Matchu
a9f44c0aa6
This doesn't affect a lot right now, it was previously defaulting to UTC I think? And I've confirmed that, while timestamps are stored in the database as UTC, they're not interpreted any differently with this setting. (Or, rather, it's loaded as a `DateTime` object for the same moment in time, but in the NST time zone. Good!) But this feels like a more useful default for displaying things for development etc, and moreover, I'm working on some logic for things like "when do limited-time Dyeworks items expire exactly?", and that logic is made *much* simpler if we can just compare dates in NST by default rather than fudge around with the zones on them and figuring out the correct midnight! (Although, as I type this, I think I maybe have thought of an easier way to do it? So maybe this change won't actually be necessary for that, but it still feels like a more sensible default for us regardless!) |
||
---|---|---|
.devcontainer | ||
.husky | ||
app | ||
bin | ||
config | ||
db | ||
deploy | ||
lib | ||
public | ||
test | ||
vendor | ||
.eslintrc.json | ||
.gitignore | ||
.ruby-version | ||
.yarnrc.yml | ||
config.ru | ||
falcon.rb | ||
Gemfile | ||
Gemfile.lock | ||
LICENSE.md | ||
package.json | ||
Procfile.dev | ||
Rakefile | ||
README.md | ||
yarn.lock |
Dress to Impress
Oh! We've been revitalizing the Rails app! Fun!
There'll be more to say about it here soon :3