Parser for ChangeLog (Markdown)
Parse changelog to object
Parse CHANGELOG files from markdown to JSON.
AI-powered changelog ai MCP server for agents. Supports parse changelog, generate entry, bump version. By MEOK AI Labs.
Parse raw conventional commits.
Highlighting system for Lezer parse trees
Parse a changeset file's contents into a usable json object
Incremental parser
JavaScript parser, mangler/compressor and beautifier toolkit for ES6+
Get repository user and project information from package.json file contents.
Utilities for reading and parsing Changeset's config
Command line tool for generating a changelog from git tags and commit history
Parse HTML character references
Angular preset for conventional-changelog.
JavaScript parser and stringifier for YAML
JSON.parse with context information on error
Utility functions for sv
Small footprint URL parser that works seamlessly across Node.js and browser environments
Node.js path.parse() ponyfill
Conventionalcommits.org preset for conventional-changelog.
Relaxed JSON is strict superset JSON, relaxing strictness of valilla JSON
Write logs based on conventional commits and templates.
Parse the Forwarded header (RFC 7239) into an array of objects
An Esprima-compatible JavaScript parser built on Acorn
Uses a grammar describing the keep-a-changelog format to attempt to parse a given file.
A rubygem to parse CHANGELOGs in my style
Parse changelog memo text.
Parse changelog files and extract entries matching various criteria
A Ruby gem for parsing changelog files. Supports Keep a Changelog format, markdown headers, and custom patterns.
Tool for parsing changelogs that are based on the keepachangelog.com standard. Changelogs can be dumped to JSON or YAML.
Vandamme is aware of files content, and will be mostly used to parse changelog files and extract relevant content.
Parse a changelog and send it via mandrill
Parse Keep a Changelog formatted markdown files with version querying, category management, release creation, and markdown write-back support.
It taks the output from git-log, parses it, and output with the standard format of changelog.
A changelog parser written in ruby with a few simple goals: 1. Parse CHANGELOG files on GitHub that follow the https://keepachangelog.com format. 2. Model the releases to able to differentiate between the various Added, Changed, Removed, etc. categories. 3. Provide a simple query interface to to access releases. 4. Provide enhanced content for particular formatted data (e.g. linking issues/pull requests). 5. Provide a simple set of tools to help manage the CHANGELOG file itself.
# Excel to Code [](https://travis-ci.org/tamc/excel_to_code) excel_to_c - roughly translate some Excel files into C. excel_to_ruby - roughly translate some Excel files into Ruby. This allows spreadsheets to be: 1. Embedded in other programs, such as web servers, or optimisers 2. Without depending on any Microsoft code For example, running [these commands](examples/simple/compile.sh) turns [this spreadsheet](examples/simple/simple.xlsx) into [this Ruby code](examples/simple/ruby/simple.rb) or [this C code](examples/simple/c/simple.c). # Install Requires Ruby. Install by: gem install excel_to_code # Run To just have a go: excel_to_c <excel_file_name> This will produce a file called excelspreadsheet.c For a more complex spreadsheet: excel_to_c --compile --run-tests --settable <name of input worksheet> --prune-except <name of output worksheet> <excel file name> See the full list of options: excel_to_c --help # Gotchas, limitations and bugs 0. No custom functions, no macros for generating results 1. Results are cached. So you must call reset(), then set values, then read values. 2. It must be possible to replace INDIRECT and OFFSET formula with standard references at compile time (e.g., INDIRECT("A"&"1") is fine, INDIRECT(userInput&"3") is not. 3. Doesn't implement all functions. [See which functions are implemented](docs/Which_functions_are_implemented.md). 4. Doesn't implement references that involve range unions and lists (but does implement standard ranges) 5. Sometimes gives cells as being empty, when excel would give the cell as having a numeric value of zero 6. The generated C version does not multithread and will give bad results if you try. 7. The generated code uses floating point, rather than fully precise arithmetic, so results can differ slightly. 8. The generated code uses the sprintf approach to rounding (even-odd) rather than excel's 0.5 rounds away from zero. 9. Ranges like this: Sheet1!A10:Sheet1!B20 and 3D ranges don't work. Report bugs: <https://github.com/tamc/excel_to_code/issues> # Changelog See [Changes](CHANGES.md). # License See [License](LICENSE.md) # Hacking Source code: <https://github.com/tamc/excel_to_code> Documentation: * [Installing from source](docs/installing_from_source.md) * [Structure of this project](docs/structure_of_this_project.md) * [How does the calculation work](docs/how_does_the_calculation_work.md) * [How to fix parsing errors](docs/How_to_fix_parsing_errors.md) * [How to implement a new Excel function](docs/How_to_add_a_missing_function.md) Some notes on how Excel works under the hood: * [The Excel file structure](docs/implementation/excel_file_structure.md) * [Relationships](docs/implementation/relationships.md) * [Workbooks](docs/implementation/workbook.md) * [Worksheets](docs/implementation/worksheets.md) * [Cells](docs/implementation/cell.md) * [Tables](docs/implementation/tables.md) * [Shared Strings](docs/implementation/shared_strings.md) * [Array formulae](docs/implementation/array_formulae.md)