-
Notifications
You must be signed in to change notification settings - Fork 90
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
Update ESLint, Prettier, TypeScript and fix/improve their configuration files #1616
Update ESLint, Prettier, TypeScript and fix/improve their configuration files #1616
Conversation
For Node.js 16 and 18 it runs fine for me, looks like it cannot connect to Meilisearch for some reason. Regarding Node.js 14 the tests fail because the latest |
c808d06
to
bbe4ed1
Compare
I might want to revert changes from doing |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1616 +/- ##
==========================================
- Coverage 97.52% 97.50% -0.03%
==========================================
Files 22 22
Lines 850 842 -8
Branches 102 86 -16
==========================================
- Hits 829 821 -8
Misses 20 20
Partials 1 1 ☔ View full report in Codecov by Sentry. |
Okay, now whatever happens is expected. I'm really confused about |
Alright, so this is ready for review, style-check is expected to fail on |
@flevi29 Shoudn't we adapt our style check? |
Ideally someone should review my changes, who understands what is being done. After that I remove all the unnecessary explainer comments and run the formatter, so that there may be no more CI errors (other than perhaps codecov, but that's probably looking at scripts rather than code, so it can be ignored). If no one at meili is around who really understands this stuff, then I guess it's entirely up to you and @brunoocasali if you trust the PR or not. If you don't understand something that I haven't quite explained via comments, ask away. |
Hello @flevi29 sorry for the delay, we have a lot on our plate currently @brunoocasali will review it when he will find the time. Currently, it's complex regarding our time, but we don't forget you! |
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.
I understood the proposal not to run the changes in the same PR. Thanks for that!
I'm approving this PR. Thanks a lot for your help and sorry for the huge delay!
"fmt": "prettier -c ./**/*.{js,ts,tsx}", | ||
"fmt:fix": "prettier -w ./**/*.{js,ts,tsx}", |
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.
I would just ask to remove this ,tsx
because it will prevent running the command later:
[error] No files matching the pattern were found: "./**/*.tsx".
"fmt": "prettier -c ./**/*.{js,ts,tsx}", | |
"fmt:fix": "prettier -w ./**/*.{js,ts,tsx}", | |
"fmt": "prettier -c ./**/*.{js,ts}", | |
"fmt:fix": "prettier -w ./**/*.{js,ts}", |
Unless you have a way to fix it without removing!
1648: Update version for the next release (v0.39.0) r=brunoocasali a=meili-bot ## 🚀 Enhancements * feat: hybrid search improvements for v1.8.x (#1647) `@mdubus` * Add `null` to Embedder type (#1646) `@amit-ksh` * Add searchCutoffMs index setting (#1643, #1645) `@amit-ksh` ```js client.index('movies').getSearchCutoffMs() client.index('movies').updateSearchCutoffMs(150) client.index('movies').resetSearchCutoffMs() ``` ## ⚙️ Maintenance/misc * Update ESLint, Prettier, TypeScript and fix/improve their configuration files (#1616) `@flevi29` * Fix code style after configuration changes (#1638) `@brunoocasali` Thanks again to `@amit-ksh,` `@brunoocasali,` `@curquiza,` `@flevi29,` `@mdubus,` `@meili-bors[bot]` ! 🎉 Co-authored-by: meili-bot <[email protected]>
1652: Update crypto statement to fix vite issue r=curquiza a=brunoocasali After the introduction of this PR #1616 we had a bunch of issues related to vite configuration on client projects as shown here meilisearch/meilisearch-js-plugins#1299 This PR introduces the rollback needed to fix the consumer's code. If this change is not enough, I will completely reverse the PR 1616. Edit: I was able to solve the issue, by using this branch with this [reproduction repo](https://github.com/flexchar/meili-issue-1299) I could build the project and also run the application without any issue. But this change introduces some breaking changes in the JWT code: Now it is required to use await: `await client.generateTenantToken(..)` instead of just `client.generateTenantToken(..)`. Co-authored-by: Bruno Casali <[email protected]>
Pull Request
Related issue
Fixes #1615
What does this PR do?
Along with what is already detailed in the related issue, the PR includes a lot of comments about the why and what, most of which should be removed once clarified.
PR checklist
Please check if your PR fulfills the following requirements:
Thank you so much for contributing to Meilisearch!