summaryrefslogtreecommitdiffhomepage
path: root/lib/axlsx/workbook/worksheet
AgeCommit message (Collapse)Author
2023-04-07Fix Layout/ElseAlignmentGeremia Taglialatela
Manually fixed
2023-04-07Fix Layout/BlockAlignment offensesGeremia Taglialatela
Manually fixed
2023-04-06Fix Layout/EmptyLinesAroundAttributeAccessorGeremia Taglialatela
``` rubocop --only Layout/EmptyLinesAroundAttributeAccessor -a ```
2023-04-06Fix Layout offenses related to access modifiersGeremia Taglialatela
``` rubocop --only Layout/EmptyLinesAroundAccessModifier,Layout/AccessModifierIndentation -a ```
2023-04-06Fix Layout/CommentIndentation offensesGeremia Taglialatela
``` rubocop --only Layout/CommentIndentation -a ```
2023-04-06Fix Layout/EmptyLineBetweenDefs offensesGeremia Taglialatela
``` rubocop --only Layout/EmptyLineBetweenDefs -a ```
2023-04-06Fix Layout/EmptyLines offensesGeremia Taglialatela
``` rubocop --only Layout/EmptyLines -a ```
2023-04-06Fix Style/Encoding offensesGeremia Taglialatela
``` rubocop --only Style/Encoding -a ```
2023-04-06Fix Layout/LeadingEmptyLines offensesGeremia Taglialatela
``` rubocop --only Layout/LeadingEmptyLines -a ```
2023-04-06Fix Layout/TrailingEmptyLines offensesGeremia Taglialatela
``` rubocop --only Layout/TrailingEmptyLines -a ```
2023-04-06Remove Layout/TrailingWhitespace offensesGeremia Taglialatela
``` rubocop --only Layout/TrailingWhitespace -a ```
2023-04-06Fix Layout/EndOfLine offensesGeremia Taglialatela
``` rubocop --only Layout/EndOfLine ``` Manually fixed
2023-04-03Escape array formulasjohnnyshields
2023-04-02`escape_formulas` should handle all [OWASP-designated formula ↵johnnyshields
prefixes](https://owasp.org/www-community/attacks/CSV_Injection).
2023-03-31Add settings for escape_formulas at global, workbook, worksheet, row and ↵johnnyshields
cell levels.
2022-11-02Improve BorderCreator argsWeston Ganger
2022-10-22Fix bug in BorderCreator when second arg is nilWeston Ganger
2022-10-21Merge pull request #156 from basefarm/pivot_multiple_data_columnsNoel Peden
Prevent Excel from crashing when multiple data columns added to PivotTable
2022-10-12Resolve all TODOsWeston Ganger
2022-10-09ImprovementsWeston Ganger
2022-10-09Remove active_support dependency from axlsx_stylerWeston Ganger
2022-09-29Merge axlsx_styler gem into caxlsxWeston Ganger
2022-09-23Improve documentation for `Worksheet#styles`Stefan Daschek
Closes #166
2022-09-21Update lib/axlsx/workbook/worksheet/worksheet.rbStefan Daschek
Co-authored-by: Geremia Taglialatela <[email protected]>
2022-09-21Move worksheet name forbidden chars to a constantGeremia Taglialatela
2022-09-21Add worksheet name max length to a constantGeremia Taglialatela
Close #163
2022-07-21Prevent Excel from crashing when multiple data columns are added to PivotTableKnut Stenmark
Excel will crash unless both `colFields` and `colItems` are declared in the PivotTable xml. First `field` of `colFields` needs to be set to -2 to tell Excel that the value columns comes from individual columns and not groups. I do not know why `colItems` are needed, but when set, the Excel document opens without crashing.
2022-07-12Add `hideDropDown` alias for `showDropDown` setting, as the latter is ↵Koza
confusing to use (because its logic seems inverted).
2022-07-09Add pivot table option to sort headers (#143)James Lam
2022-03-02instance_values -> instance_values_forpjskennedy
2022-03-02Update references to use new class methodpjskennedy
2022-02-07Validate name option to be non-empty string when passed.Josef Šimánek
2022-02-06Autowidth cell calculation is now configurableTobias Egli
On the workbook you can now configure the font_scale_divisor and the bold_font_multiplier to get better results for the automatic cell width calculationb
2022-02-05Merge branch 'master' into improve_range_errorNoel Peden
2022-01-28Fix invalid xml when pivot table created with more than one column in data fieldWeston Ganger
2022-01-24Refractor to use constant based error messagesWeston Ganger
2021-12-29Fix Worksheet#name_to_cell bug which returned reversed row/col indexesWeston Ganger
2021-05-31Fix typo in row.rbPascal Andermatt
2021-03-19Implement :offset option for worksheet#add_row (#87)Agustin Gomez
2021-03-19Add support for format in pivot tables (#79)Knut I. Stenmark
2021-02-12Merge pull request #77 from rfdonnelly/fix-special-char-in-table-headerNoel Peden
Fix special characters in table header
2021-02-03Fix special characters in pivot table cache definitionRob Donnelly
2021-02-03Fix special characters in table headerRob Donnelly
2021-01-05Merge pull request #71 from artplan1/add-date-typeNoel Peden
Allow to set cell type to `date`
2021-01-05Merge pull request #70 from chi-deutschland/fix-worksheet-title-length-ruleNoel Peden
Fix worksheet title length enforcement
2020-12-10Fix calculation of worksheet name lengthLuka Lüdicke
- The previous change caused unnecessary issues - We approximate that Excel calculates the character length with UTF-16 - Fixes https://github.com/caxlsx/caxlsx/issues/67
2020-12-03Extend cell_type_from_value with sanity checksToms Mikoss
2020-11-27Add casting to dateArtem Kozaev
Add tests
2020-11-27Allow to set cell type to `date`Artem Kozaev
2020-07-27Fix type detection for floats with out-of-rage exponents (#54)Stefan Daschek
Prior to this change, strings like "1e12345" would be interpreted as float values, regardless of the actual value of the exponent (which easily could be out of range for Ruby). In case the exponent was greater than `Float::MAX_10_EXP` (usually 308), this would result in a cell of type `:float` containing the literal string `"Infinity"`. Excel can not parse such cells and therefore gives a “corrupt data” error. In case the exponent was less than `Float::MIN_10_EXP` (usually -307) the cell would contain `0.0`. This does not result in Excel throwing an error, but probably isn't the expected result either. Note that this problem is quite likely to happen when creating a worksheet with hexadecimal strings, because e.g. "1234e567" is a perfectly valid hex value. The additional range check of the exponent introduces a slight performance overhead, so I decided to split the code path: I presume parsing floats with exponents < 100 (or no exponents at all) is way more common, so this code path behaves exactly like before. Only in the case of a 3 digit exponent the additional range check is introduced.