[BUG] TypeScript Excel.Column[] type check error
See original GitHub issue🐛 Bug Report
Lib version: 4.2.0
Steps To Reproduce
sheet1.columns = [
{ key: 'account', width: 20, style: { font: tableFontStyle, alignment: alignCenter } },
{ key: 'time', width: 16, style: { font: tableFontStyle, alignment: alignCenter } }
]
/*
error msg:
type "{ key: string; width: number; style: { font: Partial<Font>; alignment: Partial<Alignment>; }; }" lack type Column props: outlineLevel, hidden, values, letter... ts(2740)
*/
The expected behaviour:
Optional parameters, not required option
Issue Analytics
- State:
- Created 3 years ago
- Reactions:13
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Get help with linked data type refresh errors - Microsoft Support
You may encounter refresh errors when you are working in a workbook with Data Types, either by manually refreshing or if Automatic Refresh...
Read more >exceljs - npm
Read, manipulate and write spreadsheet data and styles to XLSX and JSON. Reverse engineered from Excel spreadsheet files as a project.
Read more >JavaScript typeof - W3Schools
In JavaScript there are 5 different data types that can contain values: ... You can use the typeof operator to find the data...
Read more >Possible cases for Javascript error: "Expected identifier, string ...
The cause of this type of error can often be a misplaced comma in an object or array definition: var obj = {...
Read more >React Data Grid: Excel Export - Data Types - AG Grid
Excel Exporter allows you to export values into different Excel data types. ... the underlying data type Excel will display an error when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found the difference between the two versions (which caused this bug). This is version 4.1.1: And this is version 4.2.0: It seems that reverting is needed here.
A temporary solution would be downgrading to version 4.1.1