superset/superset-frontend/temporary_superset_ui/superset-ui/temporary-plugins/setupJest.js

import { configure as configureTranslation } from '@superset-ui/core';
import { configure as configureEnzyme } from 'enzyme';
import EnzymeReactAdapter from 'enzyme-adapter-react-16';

configureTranslation();
configureEnzyme({ adapter: new EnzymeReactAdapter() });
refactor: merge core superset-ui packages (#768) 1. move translation, connection, query to core (#729) 2. update encodable to remove formatter inter-dependency (#744) 3. move number-format and time-format to core (#730) 4. move superset-ui/dimension to core (#732) 5. move superset-ui/color to core (#755) 6. move superset-ui/style to core (#756) 7. move superset-ui/validator to core (#757) 8. move superset-ui/chart-composition to core (#759) 9. move superset-ui/chart to core (#760) 2020-09-03 15:02:23 -04:00			`import { configure as configureTranslation } from '@superset-ui/core';`
fix(legacy-table): avoid React DOM (#392) * fix(legacy-table): avoid React DOM `jquery.datatables` will manipulate DOMs, sometimes remove them. In case of component being reloaded with updated props, React will not be able to find those removed nodes, causing a `cannot removeChild` error. Because of the the way to assign row keys, if table shape changes (add or remove columns), React may also have difficulty match the cached nodes via keys. In general it's a bad idea to directly manipulate React rendered DOM nodes, so we better just let `jquery.datatables` handle everything. In the future, once we removed `jquery.datatables`, a pure React component will not have such issues. * fix(legacy-table): handle the case when percentMetrics is null * fix(legacy-table): linting errors * refactor: use nimbus build * test(legacy-table): add React component tests * test(legacy-table): more sophisticated cases * fix: address PR #392 comments * chore(legacy-table): clean up tests case setups Not seeing the console.warn errors anymore. So cleaning it up. Previously it was from `<SuperChart />` component, but since we have updated the test case to not use <SuperChart>, we are good now. * fix(legacy-table): misleading comment 2020-03-09 15:45:33 -04:00			`import { configure as configureEnzyme } from 'enzyme';`
			`import EnzymeReactAdapter from 'enzyme-adapter-react-16';`

			`configureTranslation();`
			`configureEnzyme({ adapter: new EnzymeReactAdapter() });`