Conversation
Doing that to be consistent with the original event types names from JavaScript. As the onClick type is click the onActiveChange event type will be activechange. Fixes: #112
Also ts-jest to 29.2.5, prettier to 3.3.3.
Convert active, content, disabled and extraClasses properties to signals. Refs #116
Covert test to vitest also. Refs: #110
- Removed per-file Apache-2.0 license headers across the project - MIT license does not require these headers, reducing boilerplate - Reference: #166
- Managed 'data-faz-loading' attribute directly in render() - Preserved beforeShow/afterShow hooks for framework users - Strategy: Prepare core for synchronous rendering and skeleton states - Reference: #115
- Implemented fast-poc-element with synchronous rendering strategy - Added POC showcase for Alert and Breadcrumb components - Verified 'display: contents' and 'data-faz-loading' lifecycle - Updated watch config for local development on port 8082 Refs: #115
- Implemented decomposed reactivity engine (bindReactive) in src/reactivity.ts - Added layout stabilization using 'display: contents' and microtask rendering - Refactored FazElement, FazFormElement, and FazPaginator to use property-based reactivity - Removed legacy signal accessors/setters and redundant boilerplate - Updated all unit tests and the POC showcase to the new API - Bumped version to 0.5.0 Fixes: #167 Refs: #115
- Introduced bindReactive engine for property-based SolidJS integration - Implemented layout stabilization using 'display: contents' and microtask rendering - Refactored FazElement, FazFormElement, and FazPaginator with full type safety - Cleaned up legacy signal accessors and boilerplate - Completed full build and updated type declarations Refs: #167
- Inlined problematic CSS dependencies in Vitest config - Prevents ERR_REQUIRE_ESM in CI environments - Maintains compatibility across Node 20, 21, and 22 Refs: #167
- Added root ssr.noExternal for problematic CSS packages - Switched Vitest pool to 'threads' for better ESM/CJS interop - Aims to resolve persistent ERR_REQUIRE_ESM in Node 21 CI Refs: #167
- Added resolution for @asamuzakjp/css-color@4.1.1 - Reverted experimental Vitest config changes - Fixes persistent ERR_REQUIRE_ESM in Node 21/22 environments Refs: #167
- Added 'bindReactive' and 'FazPaginator' to main entry point (src/index.ts) - Implemented subpath exports in package.json for modern bundlers - Ensured type declarations are correctly generated and exposed - Resolves blocking issues for downstream libraries (e.g., faz-bootstrap) Fixes: #168
- Updated version to 0.5.1 in package.json - Finalized exports and subpath mappings for external consumers - Completed full build and generated updated declaration files Refs: #168
- Exposed ./src and ./src/* in package.json exports - Restores compatibility with 0.4.3 for downstream libraries (faz-bootstrap) - Ensures unified SolidJS instance by allowing direct source imports - Bumped version to 0.5.2 Fixes: #169
Also bump vite-plugin-solid to 2.11.12.
Move host DOM mutation out of the custom element constructor so dynamic\nFazElement children can upgrade cleanly and be tracked by fazChildren.\n\nClean stale declaration build state, expose the built ESM entrypoint as\npackage main, remove axios from the showcase, and document the project\nmission plus build hardening follow-ups.\n\nFixes: #170\nFixes: #171
Replace the mutable Yarn workflow with pnpm and a committed lockfile so installs are reproducible for faz consumers. Update CI to install dependencies with a frozen pnpm lockfile, run the build before tests, and document pnpm-based development in the README. Refs: #172
Update checkout, setup-node, and pnpm setup actions to the current major versions used by the project CI. Refs: #172
Run CI against newer Node.js versions to match the pnpm migration and current runtime targets. Refs: #172
Use the intended supported Node.js versions for CI after the pnpm workflow migration. Refs: #172
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
2 participants
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.