accessorPairTypes

Reports mismatched types between getter and setter accessor pairs.

✅ This rule is included in the ts logical and logicalStrict presets.

TypeScript allows defining different types for a getter return and its corresponding setter parameter. Defining drastically different types for a getter and setter can be confusing, as it means assigning a property to itself would not work.

This rule reports cases where a getter and setter have the same name but the getter’s return type is not assignable to the setter’s parameter type.

Examples

❌ Incorre

AEcla5<3 sp ansty="le--0:#FFCB8B;--1:#1111">11Examp53< {d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEg5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0val11<()sp ansty="le--0:#7FDBCA;--1:#096E">7<2:sp ansty="le--0:#D6DEEB;--1:#403F">5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0stri53< {d ivclassNa="meec-li">nt < sp ansty="le--0:#C792EA;--1:#8844">AEretu5<3 sp ansty="le--0:#7FDBCA;--1:#096E">72thA72_val5<3;d ivclassNa="meec-li">53< sp ansty="le--0:#D6DEEB;--1:#403F">5<3}d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEs5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0val1<1(sp ansty="le--0:#D7DBE0;--1:#403F">53newVal7<2:sp ansty="le--0:#D6DEEB;--1:#403F">5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0numb1<1)sp ansty="le--0:#D6DEEB;--1:#403F">53< {d ivclassNa="meec-li">nt < sp ansty="le--0:#7FDBCA;--1:#096E">72thA72_val5<3 sp ansty="le--0:#C792EA;--1:#8844">A5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0Stri53(newValue<);d ivclassNa="meec-li">53< sp ansty="le--0:#D6DEEB;--1:#403F">5<3}d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>AEinterfa53 Config< {d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEg5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0val11<()sp ansty="le--0:#7FDBCA;--1:#096E">7<2:sp ansty="le--0:#D6DEEB;--1:#403F">5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0stri5<3;d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEs5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0val1<1(sp ansty="le--0:#D7DBE0;--1:#403F">53newVal7<2:sp ansty="le--0:#D6DEEB;--1:#403F">5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0numb1<1)sp ansty="le--0:#D6DEEB;--1:#403F">5<3;d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>

44AEc31111Exa3F<53 {divclass="Nameec-">de44A361B0v11<11() spans="tyle--0:#7FDBCA;--1:#09">6361B0st3F<53 {divclass="Nameec-">dent< spans="tyle--0:#C792EA;--1:#88">44AEre36E724<4AE. spans="tyle--0:#7FDBCA;--1:#09">6E72_v33F<53 spans="tyle--0:#D6DEEB;--1:#40">3de44A361B0v1<111( spans="tyle--0:#D7DBE0;--1:#40">3F53newV6361B0st1<111) spans="tyle--0:#D6DEEB;--1:#40">3F<53 {divclass="Nameec-">dent< spans="tyle--0:#7FDBCA;--1:#09">6E724<4AE. spans="tyle--0:#7FDBCA;--1:#09">6E72_v34<4AE= spans="tyle--0:#D6DEEB;--1:#40">3F53 newVa3F<53 spans="tyle--0:#D6DEEB;--1:#40">33< }><}di vdivclass="Nameexpressive-">44AEc31111Exa3F<53 {divclass="Nameec-">de44A361B0v11<11() spans="tyle--0:#7FDBCA;--1:#09">6361B0st3F<53 {divclass="Nameec-">dent< spans="tyle--0:#C792EA;--1:#88">44AEre36E724<4AE. spans="tyle--0:#7FDBCA;--1:#09">6E72_v33F<53 spans="tyle--0:#D6DEEB;--1:#40">3de44A361B0v1<111( spans="tyle--0:#D7DBE0;--1:#40">3F53newV6361B0st36361B0nu1<111) spans="tyle--0:#D6DEEB;--1:#40">3F<53 {divclass="Nameec-">dent< spans="tyle--0:#7FDBCA;--1:#09">6E724<4AE. spans="tyle--0:#7FDBCA;--1:#09">6E72_v34<4AE= spans="tyle--0:#D6DEEB;--1:#40">361B0St3F53(newVal3F<53 spans="tyle--0:#D6DEEB;--1:#40">33< }>

Options

This rule is not configurable.

When Not To Use It

If your project needs to model unusual relationships between data, such as older DOM types, this rule might not be for you. You might consider using Flint disable comments and/or configuration file disables for those specific situations instead of completely disabling this rule.

Further Reading

• MDN: Property accessors
• MDN: getter
• MDN: setter
• TypeScript 5.1: Unrelated Types for Getters and Setters

Equivalents in Other Linters

• ESLint: @typescript-eslint/related-getter-setter-pairs
• Oxlint: typescript/related-getter-setter-pairs