Attempting to quiet TS2339 through the utilization of the suppressExcessPropertyErrors compiler setting

Question

Attempting to quiet TS2339 through the utilization of the suppressExcessPropertyErrors compiler setting

Take a look at this code snippet:

var x = {};
x.test = 'abc';

An issue arises with the TypeScript compiler showing the error message:

TS2339: Property 'test' does not exist on type '{}'.

To tackle this warning for object literals, I assumed that adding suppressExcessPropertyErrors to the tsconfig.json file would resolve it.

Here's how I configured my tsconfig.json:

{
    "compilerOptions": {
        "suppressExcessPropertyErrors": true
    },
    ...
}

However, despite trying this solution, the compiler continues to display the same error message.

If you have any suggestions or tips, please share them! Thanks in advance :)

angular typescript ionic2

Answer 1

Answer №1

To resolve this issue, it seems that adding suppressExcessPropertyErrors to the tsconfig.json file could be a solution.

However, this only suppresses excess properties in object constructions like:

var x = {};
x = {test:'abc'};

If you specifically want to ignore this warning for object literals,

You have the option to use the any type for flexibility, such as:

var x:any = {};
x.test = 'abc';

Learn More

This practice is known as lazy object initialization, and you can explore different approaches to handle it here:

Answer 2

To resolve this issue, it seems that adding suppressExcessPropertyErrors to the tsconfig.json file could be a solution.

However, this only suppresses excess properties in object constructions like:

var x = {};
x = {test:'abc'};

If you specifically want to ignore this warning for object literals,

You have the option to use the any type for flexibility, such as:

var x:any = {};
x.test = 'abc';

Learn More

This practice is known as lazy object initialization, and you can explore different approaches to handle it here:

Answer 3

Answer №2

While I do agree with some of the points made by @basarat, I would like to also offer my own suggestions.

There are a few reasons why declaring object properties like this could be beneficial:

var x = {
  test: ''
};
x.test = 'abc';

Intellisense support is enabled, allowing you to easily see the available properties of the object when accessing it in the future.
This approach is helpful for testing purposes. It ensures that the structure of your object remains consistent throughout your project, making it easier to write tests with this in mind.
By avoiding using the `any` type and explicitly declaring object properties, you can prevent unintended overrides of existing properties with new ones.

An Explanation:

// original object x with originProp property
var x: any = {
  originProp: 'abc'
};
// creating a new object with a newProp property
x = {
  newProp:'abc'
};

Answer 4

While I do agree with some of the points made by @basarat, I would like to also offer my own suggestions.

There are a few reasons why declaring object properties like this could be beneficial:

var x = {
  test: ''
};
x.test = 'abc';

Intellisense support is enabled, allowing you to easily see the available properties of the object when accessing it in the future.
This approach is helpful for testing purposes. It ensures that the structure of your object remains consistent throughout your project, making it easier to write tests with this in mind.
By avoiding using the `any` type and explicitly declaring object properties, you can prevent unintended overrides of existing properties with new ones.

An Explanation:

// original object x with originProp property
var x: any = {
  originProp: 'abc'
};
// creating a new object with a newProp property
x = {
  newProp:'abc'
};

Attempting to quiet TS2339 through the utilization of the suppressExcessPropertyErrors compiler setting

Answer №1

Learn More

Answer №2

Similar questions

What data type should be used for process.stdin in a TypeScript/Node.js environment?

Avoid automatically opening mat-sidenav upon page load

Is there a way to eliminate text from a barcode image using JavaScript or TypeScript?

Angular 16 impacts, notifications, processes

View unprocessed HTML content - Angular 6

The Ionic search bar will only initiate a search once the keyboard is no longer in view

Angular to always show loading spinner on page load

Is it possible for node modules to access and utilize protractor parameters?

When the required attribute in Angular2 is conditional and the value is empty, the field will be adorned with the ng-valid class

Maintain the selected list item active using ngFor after it is clicked

Broken Encoding Issue with Server-Side HttpClient Response in Angular 5 Universal

What steps can I take to turn a decorated service into an injectable component?

Instructions on utilizing *ngFor for every category I have

JavaScript - Persistent memory retention issues

Issues with expanding all nodes in the Angular Treeview function by Nick Perkins in London are causing difficulties

Tips for incorporating the ternary operator in JSX of a React component while utilizing TypeScript?

How come I'm able to access the form's control within setTimeout but not outside of it?

Setting up ESLint for TypeScript to enforce the "no-unused-vars" rule

Revise regular expression for verifying addresses

Setting setSelected to true in multiple ag-grids seems to only work for the final grid