Using computed editor options instead of direct values

[aiday-mar]

No description provided.

[Copilot]

Pull request overview

This PR refactors editor line-wrapping / line-break computation to pass around computed editor options (IComputedEditorOptions) instead of individual option values, and updates affected unit tests and view model plumbing accordingly.

Changes:

• Change ILineBreaksComputerFactory.createLineBreaksComputer to accept IComputedEditorOptions + tabSize (instead of fontInfo/wrapping parameters).
• Update view model line wrapping (ViewModelLinesFromProjectedModel) and configuration-change handling to forward computed options.
• Update related browser/common line break computers and tests to use the new API shape.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/vs/editor/test/browser/viewModel/monospaceLineBreaksComputer.test.ts	Updates test setup to construct ComputedEditorOptions for the new factory signature.
src/vs/editor/test/browser/viewModel/modelLineProjection.test.ts	Updates ViewModelLinesFromProjectedModel construction to pass computed options.
src/vs/editor/common/viewModel/viewModelLines.ts	Refactors wrapping settings handling to use ConfigurationChangedEvent + computed options.
src/vs/editor/common/viewModel/viewModelImpl.ts	Updates view model construction and config-change path to pass computed options through.
src/vs/editor/common/viewModel/monospaceLineBreaksComputer.ts	Refactors monospace line break computation to read needed values from computed options.
src/vs/editor/common/modelLineProjectionData.ts	Updates the ILineBreaksComputerFactory interface to the new signature.
src/vs/editor/browser/view/domLineBreaksComputer.ts	Refactors DOM-based line break computation to read needed values from computed options.

Comments suppressed due to low confidence (1)

src/vs/editor/test/browser/viewModel/monospaceLineBreaksComputer.test.ts:80

• This test now sets EditorOption.wordWrapColumn, but the line breaking code should be driven by the effective wrapping column (EditorOption.wrappingInfo.wrappingColumn). Once the production code is corrected to use wrappingInfo, update the test to write a wrappingInfo value (with wrappingColumn: breakAfter) instead of setting wordWrapColumn directly.