Repository navigation
feature: tree stack implementation - #1
Merged
Merged
Conversation
…nd next method updates
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 pull request introduces the initial implementation of the
tree-stackpackage, providing a lightweight, configurable utility for rendering hierarchical tree-view prefixes. It includes the coreTreeStackclass, comprehensive documentation, automated tests, and CI/CD workflows for versioning and publishing. The most important changes are:Core Implementation:
TreeStackclass inmod.ts, supporting configurable branch characters and methods for managing tree hierarchy state (enter,leave,next), along with TypeScript types and JSDoc documentation.Documentation:
README.mdwith installation instructions, usage examples, API documentation, and customization options.LICENSEfile.Testing:
mod.test.tscovering all core behaviors, edge cases, and formatting scenarios.Tooling & Automation:
deno.jsonwith package metadata, build/lint/test scripts, and import maps.ci.yml), version bumping (bump.yml), and publishing to npm/JSR (publish.yml). [1] [2] [3]Development Environment:
.devcontainerand.vscodeconfiguration files to support Deno development in VS Code with recommended extensions. [1] [2] [3][Copilot is generating a summary...]