Describe the bug
With multiple pure-documentation MDX docs, the scroll position of the preview window does not reset when switching between docs.

To Reproduce
Steps to reproduce the behavior:

1. Create at least two MDX docs without stories, with content long enough to result in a scroll bar.
2. Select the first doc in the sidebar.
3. Scroll down the first document.
4. Select the

🚀 Feature Proposal

From #10123.

When we find a config file, we should also check if there is a jest entry in any sibling package.json and print a warning that it is ignored.

If using --config we should not warn.

Motivation

Helps the user have correct and consistent

Describe the bug
When I pull the resize button of the code editor, it doesn't the resize the code in the editor.

To Reproduce
Steps to reproduce the behavior:

1. Click the resize button on the code editor and drag it down
2. The code doesn't resize

Expected behavior
I expected the code to resize as I drag down the button.

Screenshots
If applicable, add screenshots to

Are you creating an issue in the correct repository?

• When in doubt, create an issue here.
• If you have an issue with the Jasmine docs, file an issue in the docs repo
  here: https://github.com/jasmine/jasmine.github.io
• This repository is for the core Jasmine framework

• If you are using a test runner that wraps Jasmine, consider filing an issue with that library if appropriate:

As an example, the "Getting started" documentation still talks about CATCH_CONFIG_MAIN macro.

@benoittgt very kindly submitted a PR to fix some spacing issues in the markdown using gofmtmd.

It should be possible to automate this as part of the build script

Hi,

It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody() function, the body argument is set to nil:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)

Is this by design, or am I looking at a missing feature?

Cheers,

Convert To Title Case was added in RF 3.2 (#2706). Unfortunately its not fully compatible with the old Should Be Title Case keyword. For example, the second test below fails with 'This Is Not OK!' is not titlecase.:

*** Settings ***
Library        String

*** Test Cases ***
Passes
    ${title} =    Convert To Title Case    This is ok.
    Should Be Title Case    $