Release/7.0#74
Merged
Merged
Conversation
…pdated related classes, methods, and tests to align with the new API. Added new `ClearData` method in `StringData`.
…nsistency and clarity.
…crape` to `ExtractAll` for improved clarity and consistency. Updated all references, methods, and tests to align with the new naming.
…hanced parsing of diverse atomic formats. Updated tests to ensure coverage for multiple argument scenarios.
…types for enhanced format checking. Updated corresponding tests to ensure complete coverage for validity checks. Refined exception handling in `Parse` methods for consistent error responses.
…erator-based splitting for improved performance and maintainability. Introduced new properties (`IsInvalid`, `IsLiteral`, `IsTag`, `IsAtomic`, `IsExpression`) for enhanced argument type checks. Updated `ArgumentType` and related APIs to align with the changes. Revised and expanded test coverage to reflect the updates.
…gument` class for improved expression parsing, and added corresponding tests for enhanced functionality and coverage.
…clarity and context. Updated associated methods, properties, enums, and exceptions. Added `NeutralText` and `NeutralTextExtensions` for tokenization support. Expanded and updated tests to cover new functionality and changes.
…ciency and added new methods for advanced token stream navigation. Enhanced `NeutralText` and `NeutralTextExtensions` with updated operator handling, additional tokenization features, and streamlined helper methods. Replaced `EOF` with `None` in `NeutralToken` for improved clarity.
…factored `NeutralStream` for iterator-based token processing, simplifying functionality and enhancing memory efficiency. Updated `TagName` with the new `Append` method and switched from concatenation to method chaining for creating hierarchical tag names throughout the codebase. Replaced unused logic in `Argument` with `NotImplementedException`. Expanded `NeutralText` test cases for broader tokenization coverage.
…gic and unused methods, simplifying the implementation. Improved `Instruction` tokenization and processing with enhanced `NeutralStream` integration. Added comprehensive tests for `NeutralStream` and updated test cases around `Instruction` and `TagName`.
…pdated associated tests to improve format checking and error handling.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This release improves
TagNameandInstructiontext parsing to correctly capture and extract nested indirect tag references found in arrays. This is accomplished by moving away from Regex pattern matching to newNeutralTextandNeutralStreamlexer/tokenization pattern.New classes that can be used to stream tokens from a string of neutral text include.
I have also updated the API for
TagNameto make the properties a little more explicit.Argumenthas also been simplified. It now mostly centers around identification of the argument value (reference, literal, expression, etc). It is now up to user to determine if an argument needs to be parsed further (expression case). This can be done by usingTagName.Parsestatic method to extract tag names from the argument expression if needed.Instructionwas also updated to just provide the mainArgumentscollection since you can filter arguments by type. I think this simplifies the API a bit as it was already getting a little confusing and circular.