Per @atsmith813's great suggestion in https://github.com/forem/forem/pull/12281, in an effort to make the specs in spec/requests/admin/configs_spec.rb more resilient to changes in our default SiteConfig values we should update them to remove the hardcoded defaults.

For example, we have

it "updates rate_limit_feedback_message_creation" do
  expect do
    post "/admin/config", params: { site_config: { rate_limit_feedback_message_creation: 3 },
                                    confirmation: confirmation_message }
  end.to change(SiteConfig, :rate_limit_feedback_message_creation).from(5).to(3)
end

We should update this to check the default value rather than the hardcoded 5

it "updates rate_limit_feedback_message_creation" do
  expect do
    default_value = SiteConfig.get_field(:rate_limit_feedback_message_creation).dig(:default)
    post "/admin/config", params: { site_config: { rate_limit_feedback_message_creation: 3 },
                                    confirmation: confirmation_message }
  end.to change(SiteConfig, :rate_limit_feedback_message_creation).from(default_value).to(3)
end

There are multiple specs that behave like this. To complete this task you should update all of them.

Describe the solution you'd like

A generic modal for rate limit warnings was added in https://github.com/forem/forem/pull/11102. It would be idea if all places in Forem that warned a user about rate limits used that model.

Start with app/services/rate_limit_checker.rb and trace back paths from there. Some examples:

• creating too many reactions too quickly
• updating an article or user too much too quickly
• following too many users too quickly

Describe the bug

When you go to update your profile you can fill in multiple fields at a time. If you fill in many of those fields and then submit form, if 1 field is invalid you will receive an error message and none of the fields will have been saved. This can be very frustrating if you spent a lot of time filling them all out and only 1 was wrong.

Error:

Fields I had previously all filled out:

To Reproduce

1. Go to edit profile page
2. Fill in multiple fields but make the summary very long.
3. Click save profile information at the bottom
4. You should receive an error that your summary was too long but nothing else was saved.

Expected behavior

We should save what we can and only skip saving those fields that are invalid.

Is your feature request related to a problem? Please describe. There are other requests for features related to Series, like enhanced UX (https://github.com/thepracticaldev/dev.to/issues/2558) or a landing page for a series (https://github.com/thepracticaldev/dev.to/issues/2424).

Along with those requests to make Series more useful, I would like a way to easily link to a series from within a post.

Describe the solution you'd like Using liquid tags to link to a Series based on the Series' slug. I imagine this would result in a card similar to the one rendered when linking to another post, but it would be tailored to the idea of a Series.

Describe alternatives you've considered Right now when I want to link to a Series, I link to the search where the search term is the Series name.

It's a hack and not great UX, but it kinda works for Series with descriptive names.

Additional context n/a

Thanks!

Describe the solution you'd like

Right now we only have one contributor badge awarded when a DEV member makes their contribution. It would be awesome to have two more milestones -- at 32 or 64 PRs merged (we can tweak those numbers).

We're working on badge designs now but anyone is welcome to work on the code part!