Tags

## [4.3.0] - 5-03-2024

### Added
- LSP client and server support for both sending and receiving document hover text requests and responses
- Python WaspNode.source method to provide access to stream or file path originating the node
- Python WaspNode.isDecorative method to allow identification of decorative nodes (e.g., `{`,`,`,`decl`, etc.)
- Initial Python InputObject Database definition layer. See [wasppy/README.md](wasppy/README.md) for more information. This allows Python application to define, deserialize, and provide input diagnostics for application input.

### Changed
- LSP IOStreamConnection to handle turning off and on standard output when needed
- EDDI comment logic where subsequent comments committed staged components
- TreeNodePool node_token_line now recursively finds first leaf if node is not already a leaf, instead of returning illegal line number (0)

### Fixed
- EDDI README example referencing incorrect '#' comment character. EDDI comment character is '!'
- LSP server to not terminate execution when it receives unrecognized method name from client
- NVIDIA CUDA compiler error by adding explicit pointer cast to Definition create_from method
- HITInterpreter setStreamName signiture

## [4.2.0] - 2-19-2024

### Added
- LSP client and server support to optionally send and receive insertTextFormat completion item parameter
- LSP server check for client snippet support capability to pick between plain text or snippet completion
- Python extension binding for SON, HIT, DDI, EDDI Interpreters, HIVE, and wrapping/insulating Interpreter class. See [wasppy](./wasppy/README.md) for details.

### Fixed
- LSP server to handle multiple documents rather than previous limitation of one input per server process

## [4.1.0] - 2-06-2024

### Added
- HIT error recovery for missing assign, value, terminator such that parse tree construction resumes if possible, but parse failures are still captured
- HIT error recovery for partial block such that parse tree construction resumes if possible, but parse failures are still captured
- Convenience function is_nested_file that checks if any NodeView is file include
- BLANK_LINE enum type and NodeView::set_type method to set type for any NodeView
- HITNodeView::token_type method to return the type of the backing token or UNKNOWN for non-terminal or out-of-range requests

### Fixed
- LSP Client method to keep URI from definition response instead of discarding it
- LSPInterpreter to create legal URI with slash starting stream name after scheme
- Format of file include error messages to be compatible for Workbench navigation
- FindNodeUnderLineColumn to not crash from traversing nodes in separate document
- NodeView Iterator and FilePush logic causing incomplete traversal for scenarios where a nested include was the first field in the file
- HIT lexer integer and float to be C++ compatible for conversion

### Changed
- LSP URI prefix to be legitimate file scheme instead of imaginary wasplsp scheme
- HIT keyed-values now requires the value to start on the same line as the key or a syntax error will be produced

## [4.0.3] - 10-05-2023

### Fixed
- HIT lexer to properly handle the double quote character specified within arrays
- HIT lexer to properly handle various scenarios of unsupported brace expressions
- HIT lexer to properly handle '$' in normal values after brace expression update

## [4.0.2] - 9-22-2023

### Added
- LSP integer constants to set CompletionItemKind and SymbolKind icons in servers

### Fixed
- LSP URI prefix to 'wasplsp://' instead of 'wasplsp:///'

## [4.0.1] - 9-19-2023

### Added
- LSP string constants to be used by derived language servers to set capabilities

### Fixed
- HIT lexer to allow the comment character in quotes without delimiting a comment

## [4.0.0] - 8-30-2023

### Changed
 - LSP rangeFormatting request to entire document formatting which breaks backward compatibility for any use of previous formatting interface

## [3.1.4] - 8-22-2023

### Fixed
- Unused variable warnings in IOStreamConnection and ThreadConnection
- Errors in LSPInterpreter document-symbols to parse-tree build logic

## [3.1.3] - 7-12-2023

### Added
- LSPInterpreter parse tree building functionality to append document symbol detail field to node name

### Fixed
- Crash of language server client by setting response type to NONE when clearing out previous response

## [3.1.2] - 6-08-2023

### Added
- jsonvalid utility for validating json-formatted input files
- Iterator operator overloads needed to fulfill the interface for range-based for loops

## [3.1.1] - 5-22-2023

### Fixed
 - Missing error check for circular input file includes to stop file open loops

### Added
- wasp2p.get_xml method for converting definition-less input to XML (excludes decorative nodes)

### Changed
- TokenPool::push method now has a `track_newline` parameter, defaulted to `true`
- NodeView/TreeNodePool set_data logic to no longer track newlines. Note added indicating formatting is not preserved once set_data is used

### Fixed
 - Logic for is_null in waspcore generic NodeView
 - HIT parameter values to allow containing ampersand
 - HIT block names to allow starting with a period
 - Issue where prior NodeView::set_data invocations containing newlines caused subsequent NodeView/Interperter::data() calls that reconstructed string using `print_from` to create a padding string involving a string size underflowed to a size too large causing an exception to be thrown

## [3.0.2] - 11-21-2022

### Fixed
 - Interpreter root and node_at to return null view for no nodes
 - WaspHit lexer for exclusive start condition newline capturing
 - WaspJson lexer for escaped backslash before last double quote
 - WaspServer capabilities to include full text document syncing

## [3.0.1] - 9-27-2022

### Fixed
- wasphit inability to use tabs as array value separators rather than spaces

## [3.0.0] - 9-15-2022
### Changed
 - Updated NodeView constructor arguments to no longer reference a const interpreter - breaks backward compatibility

### Added
 - Various HIT updates to support integration directly into the MOOSE Framework replacing the existing parser
 - NodeView::set_data method to allow modification of leaf node data in HIT, DDI, EDDI, Halite, JSON, and SON
 - DISABLE_HIT_TYPE_PROMOTION configuration option that lets MOOSE turn off WASP's object name override logic

### Fixed
 - Error in HIT parser logic that could cause an infinite loop when shorthand-names are exploded into a hierarchy

## [2.1.0] - 04-22-2022

### Added
 - HIT support for `!include filepath`
 - SON support for `import("filepath")
 - Approximately 30% memory performance improvement in TreeNodePool
 - NodeView Iterator class to enable SIREN/HIVE iterations involving nested interpreters (E.g., included/imported files)

## [2.0.3] - 03-24-2022

### Fixed
 - Missing support for lookup values in HIVE ChildCountEqual validation rule

## [2.0.2] - 03-01-2022

### Fixed
 - Missing installation of waspcore/location.hh
 - Remove requirement of 'code' parameter in LSP diagnostic processing because it should be optional

## [2.0.1] - 10-12-2021

### Fixed
 - Inheritance of template delimiters by imported sub-templates

## [2.0.0] - 8-12-2021
### Changed 
 - Gtest dependence from TriBITS to vanilla version
 - Extra repository logic from TriBITS to Git submodule 
 - FlexLexer version from 2.5.37 to 2.6.4
 - GNU BISON version from 3.0.4 to 3.7.6
 - WASP Node type of INT to INTEGER (potentially break compatibility with 1.x if you using wasp::INT)
 - Refactored VII into more generic Extra Definition Driven Interpreter (EDDI) - breaks backward compatibility
 - EDDI input parser to cache staged non decorative nodes to avoid expensive node-count loop
 - EDDI input Lexer to be 8-bit to support identifying unicode characters 
 - Refacted GetPot into latest MOOSE-revised Hierarchical Input Text (HIT) - breaks backward compatibility
 - HIT block and subblock to be equivalent
 - HIT comma is no longer a valid array separator
 - HIT semicolon is now an allowed array separator

### Added
 - waspdrive scheduler capability.
 - support for HIT shorthand object notation '[x/y/z]'
 - support for commas in HIT strings
 - support for double-quoted strings in HIT documents
 - support for more than one input and template file in waspdrive input 
 - support for EDDI input section naming and validation
 - support for parsing EDDI input list syntax `<n..m x i> 193*10` etc.
 - support for parsing EDDI include files via a list of search locations
 - support for EDDI strings that contain '+' and comments containing unicode characters
 - InputAliases STRIDE construct to support strided aliases as dictated by EDDI input


### Fixed
- wasplsp compile error in certain configurations caused by missing include of `functional`.