* Add spec for org reaction notification
* Add organization_id to notifications
* Add validations for user and org IDs
* Move comment json_data out of loop
* Use actual column names instead
* Add organization filters
* Remove extra text-align
* Add organization filtering
* Refactor to reduce complexity
* Add receiver argument to handle orgs
* Add has_many notifications for orgs
* Add follow notifications for orgs
* Add comment notifications for orgs
* Rename some tests for specificity
* Add mark org notifications as read functionality
* Add radix to parseInt
* Define json_data outside of loop
* Notify org followers of a new post as well
* Move test to proper location
* Add test for aggregated method
* Make send org reaction notification more readable
* Test the rest of the notification model
* Refactor tag adjustment spec
* Fix extra html
* Added <kbd> tag support to markdown editors in article posts and comments.
* Fixed typo in test.
* Fixed test - now compares against inner html.
* Removed .showpage-signi-cta as dead code was reinstated accidentally via git merge.
* Use sass placeholder as no need to output the .kbd class in the css.
* Reinstated original css as accidentally changed with merge.
* add more info to internal users index
* create tag show page and add tag moderation form
* fix linting
* add tag index view and alias field
* add pagination to tag index
* fix spec
- Adds the ability to add emojis using colons 😂🎉
- The emoji conversion is added to the markdown parser labor
- When no emoji is found with the alias, same text is returned
- No assets added (no emoji images), so this will only be supported when the browser supports emojis (https://blog.getemoji.com/post/57054354336/which-browsers-support-emoji)
- Emoji conversion logic is out of markdown parser labor
- Adds its own spec
* remove inline markdown rule
* broaden evaluate_inline_markdown
basically same as evaluate_markdown but without class attributes
* remove inline markdown parser
* change code block color and background
* even out code padding top/bottom
* Really simple calculate reading time function
* Move parse_it so that the number of methods in MarkdownParser is at 20
* Added test and default value for reading time
* Add basic Honeycomb initializers
* Add some basic instrumentation, capture basic IDs
* Correctly alphabetize Gemfile, embed env in dataset names
* Actually reorder Gemfile because I can read
* Add custom tracing instrumentation to RssReader
* Improve timing/tracing info in RssReader
* Even make sure Errors show up in trace if possible
* Make sure we capture this as Rails traffic
* Swap in dev/test Libhoney::Clients as appropriate
* Move context-snagging bits into lib/instrumentation.rb
* Merging Gemfile lines seems to be my Achilles heel
* Move follow and reaction aggregation into Notification model to avoid re-compute
* Ugh. Fixing schema
* Update tests
* Skip some tests in notifications_spec
* Remove stream and add new notification views
* Actually remove Stream
* Move followers query to async method
* Remove unused tests and fix query
* Try using without delay instead
* Add without delay and escape HTML
* Make all tests pending for now
* Basic proof of concept
* Use Octokit instead of HTTParty
* add rake task
* DEV Community iOS App should be checked too
* This only need to be computed once
* Add spec
* for consistency sake
* Use timezone aware datetime methods
* Use timezone aware date parse for GitHub issue tag
* Introduce a bit of chaos programming using Zonebie
Zonebie uses a random timezone to run tests, it's a really good way to see if the code is timezone dependent or not.
* Convert GitHub issue date as UTC
* disallow nil reactables to be saved
* investigation wip
* passes deleted comment info to async bust cache
* fixes failing cache buster spec
* Create user_delete_a_comment_spec.rb
* Fix broken spec
* Binstub RuboCop
* Do not save comments when they are getting destroyed
* break update_reactable into smaller methods
