material 0.9.24 → 0.9.26

package/.editorconfig

@@ -0,0 +1,36 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+trim_trailing_whitespace = true
+
+# JavaScript files
+[*.js]
+indent_style = space
+indent_size = 2
+quote_type = single
+
+# JSON files
+[*.json]
+indent_style = space
+indent_size = 2
+
+# YAML files
+[*.{yml,yaml}]
+indent_style = space
+indent_size = 2
+
+# Markdown files
+[*.md]
+trim_trailing_whitespace = false
+
+# Package files
+[package.json]
+indent_style = space
+indent_size = 2

package/.zed/README.md

@@ -0,0 +1,64 @@
+# Zed Editor Settings for Material Library
+
+This directory contains project-specific settings for the [Zed Editor](https://zed.dev/).
+
+## Features
+
+### Auto-formatting on Save
+
+JavaScript files are automatically formatted using **ESLint with Standard JS rules** when you save them.
+
+- **Formatter**: ESLint (`eslint --stdin --fix`)
+- **Format on save**: Enabled
+- **Indentation**: 2 spaces (no tabs)
+- **Trailing whitespace**: Removed on save
+- **Final newline**: Ensured on save
+
+### How It Works
+
+The `settings.json` configures Zed to:
+1. Use ESLint as the external formatter
+2. Apply Standard JS rules via ESLint config
+3. Format automatically on save
+4. Enable ESLint LSP for real-time feedback
+
+### Manual Formatting
+
+You can also format manually:
+- **Command Palette**: `Format Document`
+- **Keyboard shortcut**: Check Zed's keybindings
+
+### Standard JS Rules
+
+The formatter follows [Standard JS](https://standardjs.com/) rules via ESLint:
+- No semicolons
+- Single quotes for strings
+- 2 space indentation
+- Space after function name
+- And more...
+
+Project-specific globals are defined in both:
+- `eslint.config.js` - for ESLint/Zed
+- `package.json` under `standard` - for Standard CLI
+
+## Requirements
+
+- Zed Editor
+- Node.js or Bun installed
+- ESLint and Standard JS installed (via `bun install`)
+
+## Troubleshooting
+
+If formatting doesn't work:
+1. Ensure dependencies are installed: `bun install`
+2. Test ESLint manually: `npx eslint src/module/extract.js`
+3. Test Standard JS manually: `npx standard src/module/extract.js`
+4. Restart Zed Editor
+5. Check Zed's output panel for errors
+
+## More Info
+
+- [Zed Editor Documentation](https://zed.dev/docs)
+- [ESLint](https://eslint.org/)
+- [Standard JS](https://standardjs.com/)
+- [EditorConfig](https://editorconfig.org/)

package/.zed/settings.json

@@ -0,0 +1,42 @@
+{
+  "languages": {
+    "JavaScript": {
+      "formatter": {
+        "external": {
+          "command": "npx",
+          "arguments": [
+            "eslint",
+            "--stdin",
+            "--fix",
+            "--stdin-filename",
+            "{buffer_path}"
+          ]
+        }
+      },
+      "code_actions_on_format": {
+        "source.fixAll.eslint": true
+      },
+      "format_on_save": "on",
+      "tab_size": 2,
+      "hard_tabs": false
+    }
+  },
+  "lsp": {
+    "eslint": {
+      "settings": {
+        "experimental": {
+          "useFlatConfig": true
+        },
+        "validate": "on",
+        "run": "onType",
+        "format": {
+          "enable": true
+        }
+      }
+    }
+  },
+  "tab_size": 2,
+  "hard_tabs": false,
+  "remove_trailing_whitespace_on_save": true,
+  "ensure_final_newline_on_save": true
+}

package/CONTRIBUTING.md

@@ -0,0 +1,125 @@
+# Contributing to Material
+
+Thank you for your interest in contributing to Material! This document provides guidelines and information about our development workflow.
+
+## Development Setup
+
+### Prerequisites
+
+- Node.js >= 16.14.0 or Bun
+- Git
+
+### Installation
+
+```bash
+# Clone the repository
+git clone https://gitlab.com/alkaloid/material.git
+cd material
+
+# Install dependencies
+bun install
+# or
+npm install
+```
+
+## Code Style
+
+We use [Standard JS](https://standardjs.com/) style guide with ESLint for code quality and consistency.
+
+### Linting
+
+Before submitting a pull request, ensure your code passes linting:
+
+```bash
+# Check for linting errors
+bun run lint
+
+# Auto-fix linting errors (when possible)
+bun run lint:fix
+```
+
+We use [Standard JS](https://standardjs.com/) which comes bundled with ESLint and requires no configuration.
+
+### Code Style Rules
+
+- **No semicolons** - Standard JS style
+- **2 spaces** for indentation
+- **Single quotes** for strings
+- **Space before function parentheses** - `function foo () {}`
+- **Object spacing** - `{ foo: 'bar' }`
+- **No trailing whitespace**
+- **LF line endings** (Unix style)
+- **Final newline** in all files
+
+### EditorConfig
+
+We use `.editorconfig` for consistent code style across different editors. Most modern editors (including Zed, VSCode, Sublime Text) support it automatically.
+
+### Standard JS
+
+Standard JS is configured in `package.json` with project-specific globals. It includes ESLint internally, so no separate ESLint config is needed.
+
+## Browser Compatibility
+
+Material is designed for modern browsers with ES6+ support:
+- Chrome/Edge (latest)
+- Firefox (latest)
+- Safari (latest)
+
+## Testing
+
+```bash
+# Run tests (when available)
+bun test
+```
+
+## Project Structure
+
+```
+material/
+├── src/               # Source files
+│   ├── module/       # Utility modules
+│   ├── mixin/        # Reusable mixins
+│   ├── class/        # Base classes
+│   └── *.js          # Component files
+├── docs/             # Documentation
+├── packages/         # Additional packages
+└── scripts/          # Build scripts
+```
+
+## Git Workflow
+
+1. Create a feature branch from `master`
+2. Make your changes
+3. Run linting: `bun run lint:fix` (Standard JS will auto-fix most issues)
+4. Commit with descriptive messages
+5. Push and create a merge request
+
+### Commit Messages
+
+Follow conventional commit format when possible:
+- `feat: add new component`
+- `fix: resolve issue with dialog`
+- `refactor: simplify event handling`
+- `docs: update README`
+- `style: fix linting issues`
+
+## Pull Request Guidelines
+
+- Ensure all linting passes
+- Update documentation if needed
+- Keep changes focused and atomic
+- Provide clear description of changes
+- Reference related issues
+
+## Questions?
+
+Feel free to open an issue for:
+- Bug reports
+- Feature requests
+- Questions about usage
+- Suggestions for improvement
+
+## License
+
+This project is licensed under GPL-3.0. By contributing, you agree that your contributions will be licensed under the same license.