-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.x] Convert ScriptedFieldsTable and SourceFiltersTable to UI Framework components. (#11401) #11454
Conversation
Failure:
Not sure why that would be related, gonna try re-running. Jenkins, test this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noticed just one small issue
We’ve detected that the following deprecated languages are in use: {{ getDeprecatedLanguagesInUse().join(', ') }}. | ||
Support for these languages will be removed in the next major version of Kibana and Elasticsearch. | ||
We recommend converting your scripted fields to | ||
<a class="kuiLink" target="_window" ng-href="{{docLinks.painless}}">Painless</a>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…mponents. (elastic#11401) * Convert ScriptedFieldsTable and SourceFiltersTable to UI Framework components. * Remove unused Bootstrap input-group-btn class. * Fix bug that prevented 'Create Index Pattern' button text from showing up.
7dfb2d7
to
06c26c7
Compare
@Bargs Fixed! Good catch. Looks like the import path was broken (https://github.com/elastic/kibana/pull/9193/files#diff-f92a33234c1ea4b5aad7362ff29fecceR9). I didn't dig too deep but I suspect this may have been caused by the migration to named exports (https://github.com/elastic/kibana/commits/master/src/ui/public/documentation_links/documentation_links.js). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I didn't dig too deep but I suspect this may have been caused by the migration to named exports
Hmmm that's concerning. @stacey-gammon you may want to check this out in case it's an edge case your scripts could have missed elsewhere in the codebase.
Backports #11401 and makes updates to the warning introduced by #9193
Before
After