Linter configuration inconsistency with organization's class member ordering rules

[coderabbitai]

Description

There is an inconsistency between the organization's styling rules and the current ESLint configuration regarding the ordering of static methods in classes.

• According to the Y-Scope development guide, static methods might be expected to go after public methods.
• According to typescript-eslint's member-ordering rule, which is currently enforced by the linter, static methods should go directly after the constructor.

This inconsistency was discovered in PR #209 where there was a discussion about the correct placement of a static method in a class.

Proposed Solution

The ESLint configuration should be updated to align with the organization's styling rules. This likely involves customizing the rule in the ESLint configuration.

References

• PR discussion
• Y-Scope development guide
• typescript-eslint member-ordering rule