Skip to content

Conversation

@jkmassel
Copy link
Contributor

@jkmassel jkmassel commented Jan 27, 2026

I had a bunch of suggestions for #301, so consider this a very large "suggest" review block.

Namely:

  1. Fetching anything from the remote should be done by an EditorHttpClient because it'll automatically deal with stuff like "make sure there's an auth header included for private sites".
  2. Now that we're doing IO, the EditorAssetBundleProvider needs synchronization, so it's all @MainActor now. This means we don't need to do log coalescing (or locking) because it's all on the main thread. This also removes concurrency warnings.

I tested this against jetpack.wpmt.co using the demo app and it still works ok.

@jkmassel jkmassel requested a review from dcalhoun January 27, 2026 23:23
Copy link
Member

@dcalhoun dcalhoun left a comment

Choose a reason for hiding this comment

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

Works well in my testing. Thank you for sharing these suggestions. Very helpful for me. I learned valuable iOS practices.

}
task.resume()

self.runningTasks.append(taskHandle)
Copy link
Member

Choose a reason for hiding this comment

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

I perceive these are never removed/emptied. Is there a memory leak concern? Should we concern ourselves with cleaning these up at some point or is the risk negligible?

@dcalhoun dcalhoun merged commit f706cb9 into fix/mitigate-crash-from-unsafe-assets Jan 28, 2026
@dcalhoun dcalhoun deleted the suggestions/301 branch January 28, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants