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?

@cchaos Done :)

@thompsongl @cchaos Updated the exporting

jenkins test this

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

@shrey Does the pre-commit hook script run for you? Both the prettier error and the import/export error from earlier should have been caught by the script that runs before allowing a commit.
If you use a GUI for git things (like Tower or Sourcetree) and it isn't running, let me know.

@shrey Does the pre-commit hook script run for you? Both the prettier error and the import/export error from earlier should have been caught by the script that runs before allowing a commit.
If you use a GUI for git things (like Tower or Sourcetree) and it isn't running, let me know.

No actually I used `git commit -m "" -n" to commit the changes, I thought that an error wouldn't occur and also because the normal commit take a lot of time, although I'll use from now on. The tests failed though :/ Should I make any changes @thompsongl

Should I make any changes

yarn lint-fix should get the error fixed. And when you commit after that, the pre-commit hook will make sure there are no other errors.

@thompsongl Done :)

jenkins test this

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

@thompsongl Tests passed :)