UNPKG

read-excel-file

Version:

Read `.xlsx` files in a web browser or in Node.js

34 lines (31 loc) 1.53 kB
"use strict"; Object.defineProperty(exports, "__esModule", { value: true }); exports["default"] = parseCells; var _xlsx = require("../xml/xlsx.js"); var _parseCell = _interopRequireDefault(require("./parseCell.js")); function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { "default": obj }; } function parseCells(sheetDocument, sharedStrings, styles, epoch1904, options) { var cells = (0, _xlsx.getCellElements)(sheetDocument); if (cells.length === 0) { return []; } // It seems like the idea of parsing "merged cells" was abandoned without being finished. // Here, it seems to just get to the stage of parsing merged cell coordinates. // Perhaps it's because it's not clear how would the package return merged cell results. // I.e. should it just duplicate the value in each one of the merged cells? // Or should it keep the existing behavior of only returning the value of the top-most left-most cell // and then return `null` for the other ones? // Perhaps the latter (existing) approach was found to be the most sensible. // // const mergedCells = getMergedCellCoordinates(sheetDocument) // for (const mergedCell of mergedCells) { // const [from, to] = mergedCell.split(':').map(parseCellCoordinates) // console.log('Merged Cell.', 'From:', from, 'To:', to) // } return cells.map(function (element) { return (0, _parseCell["default"])(element, sheetDocument, sharedStrings, styles, epoch1904, options); }); } //# sourceMappingURL=parseCells.js.map