Adding whitespace prop to EuiCodeBlockProps

[ashikmeerankutty]

Summary

Fixes #4473

• Added whitespace prop to EuiCodeBlockProps

Checklist

• Check against all themes for compatibility in both light and dark modes
• Checked in mobile
• Checked in Chrome, Safari, Edge, and Firefox
• Props have proper autodocs and playground toggles
  - [ ] Added documentation
  - [ ] Checked Code Sandbox works for the any docs examples
  - [ ] Added or updated jest tests
  - [ ] Checked for breaking changes and labeled appropriately
  - [ ] Checked for accessibility including keyboard-only and screenreader modes
• A changelog entry exists and is marked appropriately

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[thompsongl]

Thanks, @ashikmeerankutty!
Asking because I know you are capable 😉 :

Could you look into refactoring the types for code_block, code, and _code_block to avoid bugs like this in the future?
Here's the idea:
The types for EuiCodeBlock and EuiCodeBlockImpl are identical except for inline (inline?: boolean for EuiCodeBlockImpl; inline?: false; for EuiCodeBlock). We're currently duplicating type definitions in both files..
The types for EuiCode are a subset of the types of EuiCodeBlockImpl: language, transparentBackground, and inline. Again, only inline is different (inline?: boolean for EuiCodeBlockImpl; inline?: true; for EuiCode).
Essentially, both could extend from a EuiCodeBlockImpl type interface.

No problem if you can't take it on. Just let me know and I'll push a commit to this branch.

[ashikmeerankutty]

@thompsongl Thanks for the review. I will refactor those types and push.

[ashikmeerankutty]

@thompsongl Sorry for the delay, It seems to be the only difference between EuiCodeBlock and EuiCode is the inline prop. For EuiCodeBlock it is false and EuiCode it is true. So do we actually need to expose the inline prop for both ?.

[thompsongl]

So do we actually need to expose the inline prop for both ?

Nope. It's not possible to change the inline value for either, so it's not necessary to expose in the props table.

[thompsongl]

This is much cleaner; than you!

[ashikmeerankutty]

@thompsongl Updated the PR with the changes requested. Please do review.

[thompsongl]

jenkins test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4475/

[thompsongl]

LGTM!
Thanks, @ashikmeerankutty!

[thompsongl]

jenkins test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4475/

[thompsongl]

jenkins test this

flaky

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4475/