* allow codesandbox to accept runonclick
- runonclick=1 lets the user load the codesandbox when they decide
- added runonclick tests to spec
* documentation to editor_guide
* Use better description for test
* Test for new profile_updated_at touches
* Touch profile_updated_at when removing an auth
* Touch profile_updated_at when authing w/ new social username
* Use published scope for articles
* Fix variable name
* The sequencing in the union query matters
* Fix spec
* Restore a published: true condition
* This test is actually misleading due to the union
* Revert this change, not sure why it's not a relation
* Fix useless diff
* add moderation email list columns
* automate tag moderator mailing list
* reorder logic for tag mod list
* add community mod list
* remove trusted privileges when reverting a user to a regular member
* automatically make tag mods community mods
* fix merge conflicts
* add community view
* make methods less complex based on code climate sugggestion
* add specs
* refactor tag moderator module
* fix spec
* Add specs for single article functionality
* Add single article functionality
* Use article_id instead of single_article_id
* Add published: true when querying for one article
* Use article_id in specs oops
* Set users email to nil instead of blank
* Remove uniqueness validation duplication for users
* Fix organization following test in case the name contains quotes
* Add tech support role
* Add tech support permission method
* Enabled /delayed_job for tech support users
* Fix typo oops
* Add tests for tech support viewing /delayed_job
* Fix typo again...
* Rename tech role to tech admin
* Fixed fluid-comments
the inline fluid-comments in dark mode are now matching the syntax followed in the default theme.
* grey -> gray
* Added lighten function to fallback variable
Added lighten function to the fallback variable for anchor tags in fluid-comments
* Switch from deprecated honeycomb-rails to honeycomb-beeline
* Improve error handling, tests and add refactoring
* Fix multiple fetching test and add one more
The test wasn't actually testing the correct behavior, because the class
by default force fetches. It worked because it wasn't reloading the user
from the database.
* Test that Honeycomb's client is doing its thing
* Use some defensive programming to avoid any possible problem during shutdown
* Fix typo
* Use the new API to add fields to the current measured event
* Use default instrumentation and add user info to event
* Replace user.email with user.username, less personal data around
* Use mocking instead of calling Honeycomb.init
* Freeze time before traveling
* Remove a flaky test dependent on rand
* Fix Style/FormatString and Style/TrivialAccessors
* Fix Style/NegatedIf and Style/DoubleNegation
* Style/ClassAndModuleChildren is already enabled by default
* Fix Style/GlobalVars
* Group all style/ cops inside rubocop config file
* set up video route
* add video index
* update styling
* fix mobile full width styling
* bust cache when new video is created
* add unlimited scrolling
* Add basic tests for Analytics service
* User/Organization are always required
* Add some data to the test
* Use queries and date times
* Fix AnalyticsService interface in the controller
* s/HTTP_API_KEY/api-key
* Defend against nils and support datetime objects
* Update app/services/analytics_service.rb
Co-Authored-By: rhymes <rhymesete@gmail.com>
* Use SQL sum, not Rails sum
* Group average_read_time
* Use SQL, not Rails
* Use ISO date
* Fix specs
