Skip to content

refactor: rename project-specific preset to custom - #4

Merged
gabriensymons merged 1 commit into
mainfrom
release/0.2.0
Aug 14, 2026
Merged

gabriensymons merged 1 commit into
mainfrom
release/0.2.0

Conversation

@gabriensymons

Copy link
Copy Markdown
Owner

Summary

  • rename the built-in project-specific preset identifier to custom
  • update Playground values, examples, unit tests, and browser tests
  • align historical changelog terminology with custom configuration language
  • bump the package to 0.2.0 because this is a breaking pre-1.0 preset rename

Verification

  • zero case-insensitive old-term matches in current repository files, filenames, rebuilt dist, or packed package
  • 60 tests pass
  • npm pack dry-run contains 25 expected files
  • preset behavior is preserved under custom
  • independent pre-commit review passed

Remove the remaining project-specific terminology from package presets, Playground sources, tests, and changelog, and bump the breaking pre-1.0 release to 0.2.0.
@gabriensymons
gabriensymons merged commit f1eb61f into main Aug 14, 2026
3 checks passed
@gabriensymons
gabriensymons deleted the release/0.2.0 branch August 14, 2026 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant