@api-client/ui 0.5.39 → 0.5.40

package/.github/workflows/release.yml

@@ -1,82 +0,0 @@
-name: Manual Release
-
-on:
-  push:
-    tags:
-      - 'v*'
-
-env:
-  FORCE_COLOR: 1
-
-jobs:
-  test:
-    name: Test
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: 'npm'
-      
-      - name: Install dependencies
-        run: npm ci
-      
-      - name: Install playwright browsers
-        run: npx playwright install --with-deps
-      
-      - name: Run tests
-        run: npm test
-
-  release:
-    name: Create Release
-    needs: test
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      issues: write
-      pull-requests: write
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GITHUB_TOKEN }}
-      
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: 'npm'
-          registry-url: 'https://registry.npmjs.org'
-      
-      - name: Install dependencies
-        run: npm ci
-      
-      - name: Build
-        run: npm run build
-      
-      - name: Generate changelog
-        id: changelog
-        run: |
-          echo "changelog<<EOF" >> $GITHUB_OUTPUT
-          npx conventional-changelog-cli@latest release --preset conventionalcommits --release-count 1 >> $GITHUB_OUTPUT
-          echo "EOF" >> $GITHUB_OUTPUT
-      
-      - name: Create Release
-        uses: softprops/action-gh-release@v2
-        with:
-          body: ${{ steps.changelog.outputs.changelog }}
-          draft: false
-          prerelease: false
-          generate_release_notes: false
-      
-      - name: Publish to npm
-        run: npm publish --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} 

package/.prettierrc.js

@@ -1,14 +0,0 @@
-/**
- * @see https://prettier.io/docs/configuration
- * @type {import("prettier").Config}
- */
-export default {
-  trailingComma: 'es5',
-  semi: false,
-  singleQuote: true,
-  useTabs: false,
-  quoteProps: 'consistent',
-  bracketSpacing: true,
-  arrowParens: 'always',
-  printWidth: 120,
-}

package/.vscode/settings.json

@@ -1,18 +0,0 @@
-{
-  "cSpell.words": [
-    "debouncer",
-    "iconbutton",
-    "itemschange",
-    "openentity",
-    "popovertarget",
-    "querycomplete",
-    "selectedcontent",
-    "startactivity",
-    "startactivityforresult",
-    "typescale"
-  ],
-  "vscode-wtr-runner.testRunnerCommand": "npm run tsc:all && npx wtr --playwright --browsers \"chromium\"",
-  "geminicodeassist.customCommands": {
-    "add-comments": "add comments to my code. add examples whenever reasonable. focus on another developer understanding what the function is about. don't forget about class fields."
-  }
-}

package/RELEASE.md

@@ -1,163 +0,0 @@
-# Release Guide
-
-This project uses an **automated release system** with conventional commits and GitHub Actions. Releases are automatically created when changes are merged to the main branch.
-
-## 🚀 Automated Releases (Recommended)
-
-### How It Works
-
-1. **Push to main branch** (usually via PR merge)
-2. **Tests run automatically** to ensure quality
-3. **System analyzes commit messages** since the last release
-4. **Release type is determined automatically:**
-   - `major` - if commits contain "breaking:" or "!:"
-   - `minor` - if commits contain "feat:" (new features)
-   - `patch` - for all other changes (bug fixes, docs, etc.)
-5. **Release is created automatically** with changelog and npm publish
-
-### Commit Message Examples
-
-```bash
-# Major release (breaking changes)
-git commit -m "feat!: remove deprecated API"
-git commit -m "feat: new system
-
-BREAKING CHANGE: Old methods no longer work"
-
-# Minor release (new features)
-git commit -m "feat: add OAuth2 support"
-git commit -m "feat(auth): implement JWT tokens"
-
-# Patch release (bug fixes, docs, etc.)
-git commit -m "fix: resolve memory leak"
-git commit -m "docs: update API documentation"
-git commit -m "chore: update dependencies"
-```
-
-### What Happens Automatically
-
-1. ✅ Tests run to ensure everything works
-2. ✅ Version is bumped in `package.json`
-3. ✅ Changes are committed with conventional commit message
-4. ✅ Git tag is created (e.g., `v1.2.3`)
-5. ✅ GitHub release is created with automated changelog
-6. ✅ Package is published to npm
-
-## 🔧 Manual Releases (Fallback)
-
-If you need to create a release manually (e.g., for hotfixes or special releases):
-
-### Option 1: Use the release script
-
-```bash
-# Create a patch release (bug fixes)
-npm run release:patch
-
-# Create a minor release (new features)
-npm run release:minor
-
-# Create a major release (breaking changes)
-npm run release:major
-
-# Or use the default (patch)
-npm run release
-```
-
-### Option 2: Manual tag creation
-
-```bash
-npm run build
-# Update version in package.json
-npm version patch --no-git-tag-version
-
-# Commit the change
-git add package.json
-git commit -m "chore: bump version to X.Y.Z"
-
-# Create and push tag
-git tag vX.Y.Z
-git push origin main
-git push origin vX.Y.Z
-```
-
-## 📋 Conventional Commits
-
-The release system uses conventional commits to generate changelogs. Your commit messages should follow this format:
-
-```plain
-type(scope): description
-
-[optional body]
-
-[optional footer]
-```
-
-### Commit Types
-
-- `feat`: New features (triggers minor release)
-- `fix`: Bug fixes (triggers patch release)
-- `docs`: Documentation changes
-- `style`: Code style changes (formatting, etc.)
-- `refactor`: Code refactoring
-- `test`: Adding or updating tests
-- `chore`: Maintenance tasks
-
-### Breaking Changes
-
-To indicate a breaking change, use either:
-
-- `!:` in the commit message: `feat!: remove deprecated API`
-- `BREAKING CHANGE:` in the commit body:
-
-  ```plain
-  feat: new authentication system
-  
-  BREAKING CHANGE: Old auth methods are no longer supported
-  ```
-
-## 🔄 Workflow Comparison
-
-| Aspect | Automated Release | Manual Release |
-|--------|------------------|----------------|
-| **Trigger** | Push to main | Tag push or script |
-| **Release Type** | Auto-detected from commits | Manually specified |
-| **Effort** | Zero - fully automated | Manual intervention |
-| **Use Case** | Regular development flow | Hotfixes, special releases |
-
-## 🛠️ Configuration
-
-The release system is configured in:
-
-- `.github/workflows/auto-release.yml` - Automated release workflow
-- `.github/workflows/release.yml` - Manual release workflow (fallback)
-- `scripts/release.js` - Manual release automation script
-- `commitlint.config.js` - Conventional commits configuration
-- `package.json` - Version management and scripts
-
-## 🚨 Troubleshooting
-
-### Common Issues
-
-1. **No release created**: Check if commits follow conventional format
-2. **Wrong release type**: Ensure commit messages use correct prefixes
-3. **Tests failing**: Release won't proceed if tests fail
-4. **Permission denied**: Ensure GitHub token has write permissions
-
-### Debugging
-
-The automated workflow logs will show:
-
-- Last tag found
-- Commits since last tag
-- Determined release type
-- Calculated new version
-
-### Rollback
-
-If you need to rollback a release:
-
-1. Delete the tag locally: `git tag -d vX.Y.Z`
-2. Delete the tag on GitHub: `git push origin :refs/tags/vX.Y.Z`
-3. Revert the version in `package.json`
-4. Commit the revert: `git commit -m "chore: revert version to X.Y.Z"`
-5. Push the changes: `git push origin main`

package/RELEASE_SETUP.md

@@ -1,235 +0,0 @@
-# Automated Release System Setup
-
-## 🎯 Overview
-
-This project now has a **fully automated release system** that:
-
-1. **Automatically detects release types** from commit messages
-2. **Creates releases on every merge to main** (when there are changes)
-3. **Generates changelogs** from conventional commits
-4. **Publishes to npm** automatically
-5. **Provides manual fallback** for special cases
-
-## 🔄 How It Works
-
-### Automated Flow
-
-```plain
-Push to main → Tests run → Analyze commits → Determine release type → Create release
-```
-
-1. **Trigger**: Any push to the `main` branch (usually PR merges)
-2. **Testing**: Full test suite runs to ensure quality
-3. **Analysis**: System examines commits since last release
-4. **Decision**: Release type determined by commit messages:
-   - `major`: Breaking changes (`!:` or `BREAKING CHANGE:`)
-   - `minor`: New features (`feat:`)
-   - `patch`: Everything else (`fix:`, `docs:`, `chore:`, etc.)
-5. **Release**: If changes exist, creates GitHub release + npm publish
-
-### Manual Fallback
-
-```plain
-Create tag → Manual release workflow → Create release
-```
-
-For hotfixes or special releases, you can still use manual methods.
-
-## 📁 Workflow Files
-
-### `.github/workflows/auto-release.yml`
-
-- **Purpose**: Main automated release workflow
-- **Trigger**: Push to main branch
-- **Jobs**:
-  - `test`: Run tests
-  - `determine-release`: Analyze commits and decide release type
-  - `release`: Create release and publish
-
-### `.github/workflows/release.yml`
-
-- **Purpose**: Manual release fallback
-- **Trigger**: Push of version tags (`v*`)
-- **Use case**: Manual releases, hotfixes
-
-### `.github/workflows/test.yml`
-
-- **Purpose**: Quality assurance
-- **Trigger**: PRs and pushes to main
-- **Jobs**: Run tests and linting
-
-## 🎯 Release Type Detection
-
-The system analyzes commit messages since the last release:
-
-### Major Release (X.0.0)
-
-```bash
-git commit -m "feat!: remove deprecated API"
-git commit -m "feat: new system
-
-BREAKING CHANGE: Old methods no longer work"
-```
-
-### Minor Release (0.X.0)
-
-```bash
-git commit -m "feat: add OAuth2 support"
-git commit -m "feat(auth): implement JWT tokens"
-```
-
-### Patch Release (0.0.X)
-
-```bash
-git commit -m "fix: resolve memory leak"
-git commit -m "docs: update API docs"
-git commit -m "chore: update dependencies"
-```
-
-## 🛠️ Configuration Details
-
-### Commit Analysis Logic
-
-```bash
-# Check for breaking changes first
-if echo "$COMMITS" | grep -q "BREAKING CHANGE\|!:"; then
-  RELEASE_TYPE="major"
-# Then check for new features
-elif echo "$COMMITS" | grep -q "^feat"; then
-  RELEASE_TYPE="minor"
-# Default to patch
-else
-  RELEASE_TYPE="patch"
-fi
-```
-
-### Version Calculation
-
-Uses the `@pawel-up/semver` package for proper semantic versioning:
-
-```javascript
-import SemVer from '@pawel-up/semver/classes/semver.js';
-const ver = new SemVer(currentVersion);
-ver.inc(releaseType);
-return ver.format();
-```
-
-### Changelog Generation
-
-Uses `conventional-changelog-cli` with the `conventionalcommits` preset:
-
-```bash
-npx conventional-changelog-cli@latest release --preset conventionalcommits --release-count 1
-```
-
-## 🔧 Setup Requirements
-
-### GitHub Secrets
-
-- `GITHUB_TOKEN`: Automatically provided
-- `NPM_TOKEN`: Required for npm publishing
-
-### Dependencies
-
-- `conventional-changelog-cli`: For changelog generation
-- `@pawel-up/semver`: For version calculation
-- `@commitlint/config-conventional`: For commit validation
-
-### Permissions
-
-The workflows require these permissions:
-
-- `contents: write` - Create releases and tags
-- `issues: write` - Update issues
-- `pull-requests: write` - Update PRs
-
-## 🚀 Usage Examples
-
-### Normal Development Flow
-
-1. **Create feature branch**
-
-   ```bash
-   git checkout -b feature/new-auth
-   ```
-
-2. **Make changes with proper commits**
-
-   ```bash
-   git commit -m "feat: add OAuth2 authentication"
-   git commit -m "docs: update authentication docs"
-   ```
-
-3. **Create PR and merge to main**
-   - PR triggers test workflow
-   - Merge triggers auto-release workflow
-   - System creates minor release automatically
-
-### Hotfix Flow
-
-1. **Create hotfix branch**
-
-   ```bash
-   git checkout -b hotfix/critical-bug
-   ```
-
-2. **Fix and commit**
-
-   ```bash
-   git commit -m "fix: resolve critical memory leak"
-   ```
-
-3. **Merge to main**
-   - System creates patch release automatically
-
-### Manual Release (if needed)
-
-```bash
-# For immediate release
-npm run release:patch
-
-# Or create tag manually
-git tag v1.2.3
-git push origin v1.2.3
-```
-
-## 🔍 Monitoring and Debugging
-
-### Workflow Logs
-
-Check the GitHub Actions tab to see:
-
-- Which commits were analyzed
-- What release type was determined
-- Why a release was or wasn't created
-
-### Common Issues
-
-1. **No release created**: No new commits since last tag
-2. **Wrong release type**: Check commit message format
-3. **Tests failing**: Release won't proceed
-4. **Permission errors**: Check GitHub token permissions
-
-### Debugging Commands
-
-```bash
-# Check last tag
-git describe --tags --abbrev=0
-
-# See commits since last tag
-git log --pretty=format:"%s" $(git describe --tags --abbrev=0)..HEAD
-
-# Check conventional commit format
-npx commitlint --edit .git/COMMIT_EDITMSG
-```
-
-## 🎉 Benefits
-
-1. **Zero manual intervention** for regular releases
-2. **Consistent release process** with proper semantic versioning
-3. **Automatic changelog generation** from commit history
-4. **Quality gates** with automated testing
-5. **Flexible fallback** for special cases
-6. **Proper audit trail** with conventional commits
-
-This setup provides a modern, automated release system that follows industry best practices and reduces manual work while ensuring quality and consistency.

package/build/src/demo/DemoPage.d.ts

@@ -1,81 +0,0 @@
-import { TemplateResult, CSSResult } from 'lit';
-import '../md/icons/ui-icon.js';
-import '../md/button/ui-button.js';
-declare const Base: (new (...args: any[]) => import("../mixins/RenderableMixin.js").RenderableMixinInterface) & (new (...args: any[]) => import("../mixins/RouteMixin.js").RouteMixinInterface) & {
-    new (): EventTarget;
-    prototype: EventTarget;
-};
-/**
- * A base class for demo pages in the API Client ecosystem.
- */
-export declare abstract class DemoPage extends Base {
-    static get styles(): CSSResult[];
-    /**
-     * Component name rendered in the header section.
-     */
-    accessor componentName: string;
-    /**
-     * Determines whether the initial render had run and the `firstRender()`
-     * function was called.
-     */
-    accessor firstRendered: boolean;
-    /**
-     * Whether or not the dark theme is active
-     */
-    accessor darkThemeActive: boolean;
-    /**
-     * For some demo pages, whether the user is authenticated in the store.
-     */
-    authenticated: boolean;
-    constructor();
-    /**
-     * Initializes media queries and observers.
-     */
-    initMediaQueries(): void;
-    protected handleMediaQuery(e: MediaQueryListEvent): void;
-    /**
-     * The callback is called when the `darkThemeActive` property change.
-     * Overwrite this function to change the theme of the demo page.
-     *
-     * Note, this is not called by the `darkThemeActive` setter. This is called during the
-     * initialization and then when the media query event is dispatched.
-     * Call this manually when changing this value in the child page.
-     */
-    protected themeActiveCallback(): void;
-    protected activateTheme(type: 'light' | 'dark'): void;
-    /**
-     * A handler for the `change` event for an element that has `checked` and `name` properties.
-     * This can be used with `ui-switch`, `ui-checkbox`, and `checkbox` elements.
-     *
-     * The `name` should correspond to a variable name to be set. The set value is the value
-     * of `checked` property read from the event's target.
-     */
-    protected _toggleBooleanOption(e: Event): void;
-    loadMonaco(): Promise<void>;
-    /**
-     * The page render function. Usually you don't need to use it.
-     * It renders the header template, main section, and the content.
-     */
-    pageTemplate(): TemplateResult;
-    /**
-     * Call this on the top of the `render()` method to render demo navigation
-     * @returns HTML template for demo header
-     */
-    headerTemplate(): TemplateResult;
-    navigationTemplate(): TemplateResult;
-    /**
-     * Abstract method. When not overriding `render()` method you can use
-     * this function to render content inside the standard API components layout.
-     *
-     * ```
-     * contentTemplate() {
-     *  return html`<p>Demo content</p>`;
-     * }
-     * ```
-     */
-    abstract contentTemplate(): TemplateResult;
-    handleAuthenticate(): void;
-    authenticateTemplate(): TemplateResult;
-}
-export {};
-//# sourceMappingURL=DemoPage.d.ts.map

package/build/src/demo/DemoPage.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"DemoPage.d.ts","sourceRoot":"","sources":["../../../src/demo/DemoPage.ts"],"names":[],"mappings":"AAAA,OAAO,EAAQ,cAAc,EAAE,SAAS,EAAE,MAAM,KAAK,CAAA;AAWrD,OAAO,wBAAwB,CAAA;AAC/B,OAAO,2BAA2B,CAAA;AAElC,QAAA,MAAM,IAAI;;;CAA2C,CAAA;AAErD;;GAEG;AACH,8BAAsB,QAAS,SAAQ,IAAI;IAEzC,MAAM,KAAK,MAAM,IAAI,SAAS,EAAE,CAE/B;IAED;;OAEG;IACS,QAAQ,CAAC,aAAa,SAAK;IAEvC;;;OAGG;IACH,SAAkB,aAAa,UAAQ;IAEvC;;OAEG;IACS,QAAQ,CAAC,eAAe,UAAQ;IAE5C;;OAEG;IACH,aAAa,UAAQ;;IAUrB;;OAEG;IACH,gBAAgB,IAAI,IAAI;IASxB,SAAS,CAAC,gBAAgB,CAAC,CAAC,EAAE,mBAAmB,GAAG,IAAI;IAKxD;;;;;;;OAOG;IACH,SAAS,CAAC,mBAAmB,IAAI,IAAI;IASrC,SAAS,CAAC,aAAa,CAAC,IAAI,EAAE,OAAO,GAAG,MAAM,GAAG,IAAI;IAgBrD;;;;;;OAMG;IACH,SAAS,CAAC,oBAAoB,CAAC,CAAC,EAAE,KAAK,GAAG,IAAI;IAMxC,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IAOjC;;;OAGG;IACM,YAAY,IAAI,cAAc;IAKvC;;;OAGG;IACH,cAAc,IAAI,cAAc;IAKhC,kBAAkB,IAAI,cAAc;IAIpC;;;;;;;;;OASG;IACH,QAAQ,CAAC,eAAe,IAAI,cAAc;IAE1C,kBAAkB,IAAI,IAAI;IAI1B,oBAAoB,IAAI,cAAc;CAMvC"}