OpenCloud
/
mastodon
mirror of https://github.com/tootsuite/mastodon
1
1
Fork 0
Code Issues Releases Wiki Activity
Your self-hosted, globally interconnected microblogging community. https://joinmastodon.org/
4,013 Commits
128 Branches
269 Tags
917 MiB
Ruby 56.5%
JavaScript 28.3%
CSS 8.5%
HTML 6.5%
Dockerfile 0.1%
 
 
 
 
 
Go to file
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
app
…
bin
…
config
…
db
…
docs
…
lib
…
log
…
nanobox
…
public
…
spec Fix StatusLengthValidator tests 2017-09-02 11:37:40 -05:00
streaming
…
vendor/assets
…
.babelrc
…
.buildpacks
…
.codeclimate.yml
…
.dockerignore
…
.editorconfig
…
.env.nanobox
…
.env.production.sample
…
.env.test
…
.env.vagrant
…
.eslintignore
…
.eslintrc.yml
…
.foreman
…
.gitattributes
…
.gitignore
…
.haml-lint.yml
…
.nanoignore
…
.nvmrc
…
.postcssrc.yml
…
.profile
…
.rspec
…
.rubocop.yml
…
.ruby-version
…
.scss-lint.yml
…
.slugignore
…
.travis.yml
…
Aptfile
…
CONTRIBUTING.md
…
Capfile
…
Dockerfile
…
Gemfile
…
Gemfile.lock
…
ISSUE_TEMPLATE.md
…
LICENSE
…
Procfile
…
Procfile.dev
…
README.md
…
Rakefile
…
Vagrantfile
…
app.json
…
boxfile.yml
…
config.ru
…
docker-compose.yml
…
docker_entrypoint.sh
…
package.json
…
scalingo.json
…
yarn.lock
…

README.md

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?