fix: Wrong condition for coordinate options

[dmtrKovalenko]

No description provided.

[what-the-diff]

PR Summary

• Improvement in Position Defining Process
  The changes have been made on how the position is being set. Earlier, position was set when both options.x and options.y were null. Now, it's been improved to do so when either options.x or options.y is precisely a number. This raises the bar for the condition to be met, hence making the system more robust.

• Corrected a Typographical Error
  The variable options.touchPosition was initially misspelled which could have led to technical glitches. This typo has been now rectified which increases the overall system efficiency.

• Enhanced Variable Definition
  The variables length and step are now being defined with higher data precision in mind. Earlier, it used an OR operator and now it's been changed to a nullish coalescing operator. This allows more specific, reliable and fault-proof data definition.

[dmtrKovalenko]

🎉 This PR is included in version 1.13.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀