Merged
Conversation
…notifications, and buckets support
- Added optional `validator` function to prop definitions for value validation. - Introduced lifecycle hooks: `beforeMount`, `beforeUpdate`, and `onError` for better component management. - Updated documentation to reflect new prop validation and lifecycle features. feat: extend reactive module with watch and readonly utilities - Implemented `watch` function to observe signal changes with access to old values. - Added `readonly` function to create read-only views of signals. - Enhanced utility functions with type guards for signals and computed values. fix: improve security measures in sanitize function - Added checks to remove dangerous tags even if explicitly allowed. - Implemented protections against DOM clobbering via reserved IDs and names. - Enhanced URL normalization to prevent bypass attempts using Unicode characters. feat: introduce new methods in BQueryElement for DOM manipulation - Added `wrap`, `unwrap`, `replaceWith`, and `scrollTo` methods for easier element manipulation. - Implemented `delegate` method for efficient event handling on child elements. test: add comprehensive tests for new features and security enhancements - Created tests for new methods in BQueryElement. - Added tests for `watch` and `readonly` functionalities in the reactive module. - Implemented tests for security improvements in the sanitize function and prototype pollution prevention in utils.
This workflow automatically marks stale issues and pull requests based on inactivity, helping to manage repository maintenance.
Add stale.yml workflow for managing inactive issues and PRs
Add GitHub Actions workflow to summarize new issues
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Add CodeQL analysis workflow configuration
- Updated `beforeUpdate` to accept props for better control during updates. - Added support for `beforeMount` lifecycle hook. - Implemented prop validation in component definition. - Introduced delegated event handling in BQueryElement with `delegate` and `undelegate` methods. - Expanded security measures by adding more dangerous tags and reserved IDs in sanitizer. - Added tests for lifecycle hooks and prop validation to ensure correct behavior.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fine-tunes the docs build and CI/CD pipeline to make static asset filenames safer for case-sensitive environments and ensure documentation is deployed consistently as part of the release flow.
Changes:
- Configure VitePress’ underlying Vite/Rollup build to use hexadecimal (
hex) hash characters for output filenames to avoid case-sensitivity issues on some servers. - Remove the event filter on the
deploy-pagesjob so GitHub Pages deployment runs whenever the workflow runs (includingreleaseevents), as long asbuild-docscompletes successfully.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/.vitepress/config.ts | Adds a vite.build.rollupOptions.output.hashCharacters = 'hex' override so generated asset hashes are strictly lowercase hexadecimal, improving compatibility with case-sensitive hosting environments. |
| .github/workflows/npm-publish.yml | Simplifies the deploy-pages job trigger by removing the if condition, allowing docs deployment to run on all configured workflow events once docs are built. |
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.
No description provided.