* remove max-width cap on .home
* remove max-width cap on .home
* Revert "Merge branch 'master' into article-css-extra-wide"
This reverts commit 3eff6e456e11f5fc74e30d25d6e01c237c3b0d83, reversing
changes made to 5e064676029f9ce630b5580e46b9d64c6f43e838.
* revert max-width and add max-width to article-show
based on andrew bone's suggestion. looks good thus far both on home and article page in various screen sizes
* Removed a modified file from pull request
* Removed a modified file from pull request
* Removed a modified file from pull request
* Removed a modified file from pull request
* Removed a modified file from pull request
* Update article-show.scss
* Use a slightly faster call for user_id
* Remove unused file
* Test receive notifications functionality
* Notify when receive_notifications is true
* Test receiving reaction notifications
* Do not notify if receive_notifications is false
* Fix test for parent comment notification
* Add article mute notifications feature
* Remove deprecated specs
* Prevent email when receive_notification is false
* Update button messaging
* Use RESTful /article_mutes patch request
* Use parent or root article instead
* Add myself to core contributors
* add myself to the core contributors
* fix to issue 1574 with the V2 editor
* fix tag bug in v2 editor
* fix v2 editor bug
* remove unused code
* Added the 'initalpath' and 'module' options to the codesandbox embed and updated the help page.
* Fixed spelling errors.
* Rework from previous PR: Improved exception text. Improved regex for detecting invalid options. Changed logic to raise an exception if any invalid options are found by moving the exception raising to be inside the valid_option() method.
* Added unit tests for codesandbox_tag.rb.
* Change worker line in procfile
* mod buildpacks
* Add bin/start-pgbouncer
* Modify procfile
* Remove bin/start-pgbouncer
* Make artice show caching more effective
* Replace find_by().nil? with exists?
find_by asks the DB and the ORM to load the entire object in memory, then it is discarded just know if it exists or not. Exists will just return true or false
* Use present? in lieu of any? when it is proper
A request for any? followed by each in a most likely full collection results in two SQL queries. present? preloads the objects, so it results in one single connection because the objects are already in memory.
* Create jsfiddle_tag.rb
Add liquid tag for jsfiddle
* Create jsfiddle_tag-spec.rb
Add liquid tag for jsfiddle
* Update _editor_guide_text.html.erb
Add liquid tag for jsfiddle
* Updates for rubocop
* Edit boilerplate
Change some of the boiler plate code.
* rubocop compliance
* Fixed name
Fixed file name
* Fixed boiler plate
Changed codepen to jsfiddle
* Update guide text
Change the Guide Text to be jsfiddle specific.
Co-Authored-By: Link2Twenty <AndrewB05@gmail.com>
* Fixed typo in spec
Co-Authored-By: Link2Twenty <AndrewB05@gmail.com>
* Update Valid Link
* Update jsfiddle_tag.rb
* Add Approved html
* Remove double slash
* Revert change
* Fix XSS error
* Remove extra line
* Remove extra slash
* Remove extra slash
* Make DRY
* rubocop compliance
* Change test logic
* Revert test to Approvals
* Fix HTML approved
* Use name attribute
* Export comments
* Update copy
* Fix time-dependent test
* Remove reactions_count from the export
* Only select needed attributes from the DB
* Add the path of the commentable to the export
Comments are attached to something but from the export that is not easily identifiable. We add the "commentable_path" to give some context.
