-
Notifications
You must be signed in to change notification settings - Fork 867
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
[nodejs client] hookup js client with dashboards #1342
Conversation
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.
This looks good Anan! I'd recommend adding descriptions for each ts-expect
, or try to eliminate those exceptions if possible. Otherwise I added some comments about the types which may not require any action but I just wanted to check.
src/core/server/saved_objects/migrations/core/build_active_mappings.test.ts
Outdated
Show resolved
Hide resolved
src/core/server/saved_objects/migrations/core/index_migrator.test.ts
Outdated
Show resolved
Hide resolved
...server/saved_objects/migrations/opensearch_dashboards/opensearch_dashboards_migrator.test.ts
Outdated
Show resolved
Hide resolved
...server/saved_objects/migrations/opensearch_dashboards/opensearch_dashboards_migrator.test.ts
Outdated
Show resolved
Hide resolved
Things I tested with this PR:
Haven't tested, saving settings restarting or exporting saved objects or importing saved objects from version OSD Also, I'm not positive if it was just my VM churning with the multiple processes I'm doing on it or my recent OpenSearch snapshot, but the loading of a dashboard seems a little bit slower than usual. Could you verify that it's just not my machine? If you do notice a difference in the load time from \m/ Awesome work! \m/ Thanks |
1.change @elastic/elasticsearch to @opensearch-project/opensearch 2.add path in tsconfig.base.json to let nodejs types point to api/new.d.ts which is the new defined types 3.fix hookup issues in src/core/server/opensearch 4.fix hookup issues in src/core/server/core_usage_data_service.ts 5.fix hookup issues in src/core/server/saved_objects fix PR comments and add more explains to type mismatch Sub-Issue Resolved: opensearch-project#1193 Sub-Issue Resolved: opensearch-project#1224 Sub-Issue Resolved: opensearch-project#1216 Issue Resolved: opensearch-project#837 Signed-off-by: Anan Zhuang <ananzh@amazon.com>
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.
This looks great Anan, thanks!
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! Like I am to start and run, on my opinion that we should get this merged in and handle in any fall out if any.
Description
This is a merged PR from feature/nodejs branch.
1.change @elastic/elasticsearch to @opensearch-project/opensearch
2.add path in tsconfig.base.json to let nodejs types point to api/new.d.ts
which is the new defined types
3.fix hookup issues in src/core/server/opensearch
4.fix hookup issues in src/core/server/core_usage_data_service.ts
5.fix hookup issues in src/core/server/saved_objects
Sub-Issue Resolved: #1193
Sub-Issue Resolved: #1224
Sub-Issue Resolved: #1216
Issue Resolved: #837
Check List
yarn test:jest
yarn test:jest_integration
yarn test:ftr