Open erichoracek opened 1 month ago
Hey, Eric. It was a deliberate change because I no longer have the resources to evolve two different implementations across the console and the standalone app, which has become largely an AppKit-based app in some important ways. I didn't want the macOS console to represent what the tool offers.
The change was mentioned in the release notes but down below because I wasn't sure if anyone used it on macOS. You should be able to still access the SettingsView
or provide ways to share the logs from a macOS app.
I'm open to potentially shipping a simplified version of the console that works close to what the iOS console does in the future versions. The iOS console is the main part of the project and is what gets the most resources, and it will be feasible to keep them updated. I've already invested time into restructuring the codebase using package
modifier to make it possible to evolve it separately from the standalone app.
Gotcha, that reasoning makes sense, and definitely understand how the Mac app is diverging from the ConsoleView
implementation and both are hard to maintain. I agree that a simplified version of the console that is basically a duplicate of what we have on the iOS app would be a good solution to enable testers to quickly diagnose issues while still allowing engineers that work on the app to have the full pulse pro app for a more robust log viewing experience
Hi, thanks for making and maintaining Pulse! It seems that the
ConsoleView
was removed for macOS in https://github.com/kean/Pulse/commit/57a948138a984cf93ac4a612915ff9f2d7110b41 — is this a temporary change or permanent? Hoping for more context as It's not mentioned in the release notes. This means that we're unable to update to Pulse 5.0, as the testers of our app are unlikely to install a companion app to view logs, and prefer the integrated console view.