Skip to content
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

Breaking out un-related changes from #1487 #1670

Merged
merged 10 commits into from
Dec 16, 2024

Conversation

jamesmaa
Copy link
Collaborator

Originally authored by @djahandarie . This basically pulls out the irrelevant changes to performance canvas PR and improves the ergonomics and readability of the original PR

@jamesmaa jamesmaa requested a review from a team as a code owner December 16, 2024 19:11
Copy link

github-actions bot commented Dec 16, 2024

Playwright test results

failed  2 failed
passed  3 passed

Details

stats  5 tests across 4 suites
duration  8 minutes, 32 seconds
commit  67a509c

Failed tests

chromium › integration.spec.js › anki add
chromium › visual.spec.js › visual

types/ext/core.d.ts Outdated Show resolved Hide resolved
@@ -43,7 +43,9 @@ export class Database {
try {
this._isOpening = true;
this._db = await this._open(databaseName, version, (db, transaction, oldVersion) => {
this._upgrade(db, transaction, oldVersion, structure);
if (structure !== null) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be part of the main PR

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like a guard clause added for type-safety and not really related to the main PR

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, the PR makes this field nullable so that we can have workers that interact with the DB but don't upgrade it. It's a logic change.

dev/data/manifest-variants.json Outdated Show resolved Hide resolved
@@ -17,6 +17,8 @@
"eslint.format.enable": true,
"javascript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false,
"typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false,
"javascript.format.enable": false,
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this shouldn't be here? I like having files formatted

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The files are still formatted, just by eslint instead of vscode's formatter. Previously they would both run and conflict and cause all sorts of issues.

@@ -9,7 +9,7 @@
"noImplicitAny": true,
"strictPropertyInitialization": true,
"suppressImplicitAnyIndexErrors": false,
"skipLibCheck": false,
"skipLibCheck": true,
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently this degrades type integrity. Could you give a reason why you've enabled this @djahandarie ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library types conflict with each other. You can see it by turning on the check. I couldn't figure out any other way to resolve this.

@@ -43,7 +43,9 @@ export class Database {
try {
this._isOpening = true;
this._db = await this._open(databaseName, version, (db, transaction, oldVersion) => {
this._upgrade(db, transaction, oldVersion, structure);
if (structure !== null) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like a guard clause added for type-safety and not really related to the main PR

@jamesmaa jamesmaa requested a review from djahandarie December 16, 2024 22:18
@jamesmaa jamesmaa added this pull request to the merge queue Dec 16, 2024
Merged via the queue into yomidevs:master with commit f391760 Dec 16, 2024
11 checks passed
@jamesmaa jamesmaa deleted the separate-changes branch December 16, 2024 23:13
@Kuuuube Kuuuube added the kind/meta The issue or PR is meta label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/meta The issue or PR is meta
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants