* Update format specifiers in readable_publish_date
* Trigger Travis manually
* Update format specifiers in readable_publish_date
* Update format specifiers in readable_publish_date
Co-authored-by: rhymes <rhymes@hey.com>
* Add fakeredis gem
* Mock Pusher::PushNotifications in specs
* Remove Redis from Travis
* Add Android tests to ConsumerApp specs
* Use mock for push notification tests and refactor ConsumerApp and Device code
* Fix remaining broken specs
* Use symbols
* Cleanup rpush helpers
* Pusher::PushNotifications is no more
* Use human friendly platform in Admin::ConsumerApps index page
I was seeing during testing this console error:
"Error: <path> attribute d: Expected path command, "…0-4 2 2 0 000 4z\\".
Removing the \" and leaving just " seems like it corrected that (the
error stops showing, the icon is unchanged since the prior path was
drawn before the error raised).
* Set opacity-0 CSS utility class to 0.00001 for ChromeVox.
* Update app/assets/stylesheets/config/_generator.scss
Co-authored-by: Vaidehi Joshi <vaidehi.sj@gmail.com>
* Added a SASS variable as it's being used in #13435.
* Revert "Added a SASS variable as it's being used in #13435."
This reverts commit ec1eaa17387b8e050ca6dae73b083823bc44f6e9.
Co-authored-by: Vaidehi Joshi <vaidehi.sj@gmail.com>
* Override the Settings::RateLimit.follow_count_daily
An interaction was occurring when the data update script test to move
these settings was run prior to the rate limit test - where the rate
limiter was created with the value 23 for the follow count, but the
settings module was reporting 500.
Stub out the database setting to an explicit value - and allow the
user follow count to be one more (so that we trigger the rate limit
and respond with a 429).
* Clear the settings cache before reading the values
This appears to correct the modification made (and reverted?) in the
data update test without requiring more changes to the context (which
remains as it was).
* Make explicit that badge slug is auto generated
* Remove slug from new form
* Remove unused disabled form field
* Remove link and Crayonsify form
* Add badge's path
* Handle GitHub "Repository access blocked" error
We've been seeing a lot of these errors on DEV, and it's a pretty
reasonable expectation that if we're being blocked from seeing them
using the user's OAuth access token that this isn't temporary.
* Re-raise so we don't swallow this error
* Constant name != company name???!?!?!
* Add required tooltips and asterisks to fields
* Generate profile image for email signups
* Use be over eq
Co-authored-by: Michael Kohl <citizen428@dev.to>
* Use path helpers over hard-coded paths
Co-authored-by: Michael Kohl <citizen428@dev.to>
* Add labels to make it more accessible
* Stub it all... eek
* stub some more stuff
* stub stub stub
* Move aria label to proper label and fix tests
Co-authored-by: Michael Kohl <citizen428@dev.to>
* Refactoring Help component
* Fixing typo
* Adding missing prop types
* Removing setCommonProps
* Moving show to parent component
* Renaming Format component
* Converting help component to functional component
* Removing html from state
* Fixing modal toggle and eslint errors
* Adding arria hidden
* Using optional chaining
* Fixing variable names
* Renaming state variable
* Adding jsdoc
Co-authored-by: Nick Taylor <nick@dev.to>
* add prefer object destructuring lint rule
* fix typo
* sweep up lint errors missed in config controller
* Revert "fix typo"
This reverts commit 44f9d57e3f0dc4007ab9020c8c659c2f770230c2.
* Revert "sweep up lint errors missed in config controller"
This reverts commit 3f8d5d782fe110607c2172b713c74c08c883eda3.
* make this a warning rather than error for now
* undo auto change
This partial is not actually rendered on the user profile, it is only
used by organizations. Moving it to the directory where other
organization-specific partials live!
Noticed the Faker book title included "No Country for Old Men" which
caused a failure expecting search for "old" to be empty (you can set
the title in the let block to replicate this).
Choose title and body that do not include "old" in order to prevent
false failures.
When we call Hash.dup the values pointed to by the keys are not
duplicated (the hash is, but the keys and values are the same).
Because the FeatureFlag enabled path is mutating the values, this is
interacting during tests.
`deep_dup` the ITEMS hash before mutating when the either of the two
menu item feature flags are enabled.
