Implement Ability for Data Editor Profiling of Unapplied and "On Disk" Data.

[stricklandrbls]

Enhancement Request: Implement Ability for Data Editor Profiling of Unapplied and "On Disk" Data.

Summary

WIth the investigation of the data profiler and which data is the target, it appears to be useful for the data editor to provide functionality to profile both unapplied data changes in the editor and current data on disk.

Proposed Solution / Description

Have an input available in the profiler to select which "data target" to profile. If the target is current unapplied data changes then the extension shall provide profiling of such data via Omega Edit API calls. For on disk data, the extension shall query on disk data and profile the profiling data to the UI.

Addtional Notes

N/A

[Ontiomacer]

I’ve implemented backend support for profiling both in-memory (unapplied) and on-disk data by conditionally creating an isolated Omega Edit session.

Next step would be wiring a UI selector in the profiler to pass the target field (editor vs disk).

Does this direction align with expectations?
@stricklandrbls

[Ontiomacer]

If yes I'll create a PR shortly.

[stricklandrbls]

@Ontiomacer By "backend support" do you mean implementations towards the Omega Edit source or the Data Editor's extension TS source? If you have some type of functionality for this I'd like to see it.

Also, if you have the Svelte UI components created for this issue then by all means go ahead and throw a PR up and I'll review it!

---

I've added you as an assignee and we can tackle it together.