aschmitz e18ed4bbc7 Fix StatusLengthValidator tests
This fixes the StatusLengthValidator tests to use
StatusLengthValidator::MAX_CHARS to derive the length of the strings
tested, and so makes them resilient to changes in MAX_CHARS (such as the
one that made these tests fail, with it being changed from 500 to 512).

This seems a bit odd for some types of tests, but appears to make sense
here, where the testing goes beyond `status.length > MAX_CHARS`.
2017-09-02 11:37:40 -05:00
2017-08-06 23:53:25 +02:00
2016-02-20 22:53:20 +01:00
2017-08-01 13:20:29 -07:00
2017-09-02 11:37:40 -05:00
2016-02-20 22:53:20 +01:00
2017-07-14 20:30:12 +02:00
2017-07-27 22:30:27 +02:00
2017-07-27 22:30:27 +02:00
2017-04-15 02:05:41 +02:00
2016-02-25 00:17:01 +01:00
2017-07-27 22:30:27 +02:00
2017-08-01 05:58:08 +02:00
2017-07-14 09:42:50 -07:00
2017-07-21 13:40:48 +02:00
2017-07-28 22:53:16 +02:00
2016-02-20 22:53:20 +01:00
2017-08-01 13:20:29 -07:00

Mastodon Glitch Edition

Now with automated deploys!

Build Status

So here's the deal: we all work on this code, and then it runs on dev.glitch.social and anyone who uses that does so absolutely at their own risk. can you dig it?

Description
Custom front end for Mastodon
Readme 222 MiB
Languages
Ruby 40.4%
JavaScript 39.5%
SCSS 15.9%
Haml 3.9%
HTML 0.1%