Raycaster: Deprecate .linePrecision.

[Peque]

Fixes #18590.

There were no previous tests for Raycaster's precision/threshold, so I added none myself. 😅

First PR in this project and very little experience with JS. Review with care... 😇

[Peque]

I ended-up pushing some tests.

[Mugen87]

Please add this code to Three.Legacy.js, otherwise user code will break.

Object.defineProperties( Raycaster.prototype, {

	linePrecision: {
		get: function () {

			console.warn( 'THREE.Raycaster: .linePrecision has been deprecated. Use .params.Line.threshold instead.' );
			return this.params.Line.threshold;

		},
		set: function ( value ) {

			console.warn( 'THREE.Raycaster: .linePrecision has been deprecated. Use .params.Line.threshold instead.' );
			this.params.Line.threshold = value;

		}
	}

} );

[Peque]

@Mugen87 Added the deprecation warning in b30437b. Seems to be working fine:

I can squash the fixup commits before merging. Feel free to squash them yourself if you prefer so.

I see you changed the MR description, so maybe you want me to change the commit subject too?

[Mugen87]

I see you changed the MR description, so maybe you want me to change the commit subject too?

No, not necessary. I've only changed the PR title since it makes my life easier when writing the release notes^^.

[Peque]

No, not necessary. I've only changed the PR title since it makes my life easier when writing the release notes^^.

@Mugen87 Understood. 😊 👍

Do you want me to squash the fixup commits and force-push the changes? I think GitHub allows you to see diffs between force-pushed changes (to verify I did not introduce new changes since your last review), but if you want to squash them yourself, I'll leave it to you.

[Mugen87]

Do you want me to squash the fixup commits and force-push the changes?

That would be great since the merge option Squash and merge is not yet enabled for this repo.

[Peque]

@Mugen87 Done. 😊

[mrdoob]

Thanks!