wexample-wex-addon-dev-css 6.0.73__tar.gz → 6.0.74__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- wexample_wex_addon_dev_css-6.0.74/PKG-INFO +229 -0
- wexample_wex_addon_dev_css-6.0.74/README.md +211 -0
- {wexample_wex_addon_dev_css-6.0.73 → wexample_wex_addon_dev_css-6.0.74}/pyproject.toml +3 -2
- wexample_wex_addon_dev_css-6.0.74/tests/.gitkeep +0 -0
- wexample_wex_addon_dev_css-6.0.73/PKG-INFO +0 -459
- wexample_wex_addon_dev_css-6.0.73/README.md +0 -442
- {wexample_wex_addon_dev_css-6.0.73 → wexample_wex_addon_dev_css-6.0.74}/src/wexample_wex_addon_dev_css/__init__.py +0 -0
- {wexample_wex_addon_dev_css-6.0.73 → wexample_wex_addon_dev_css-6.0.74}/src/wexample_wex_addon_dev_css/css_addon_manager.py +0 -0
- {wexample_wex_addon_dev_css-6.0.73 → wexample_wex_addon_dev_css-6.0.74}/src/wexample_wex_addon_dev_css/py.typed +0 -0
|
@@ -0,0 +1,229 @@
|
|
|
1
|
+
Metadata-Version: 2.1
|
|
2
|
+
Name: wexample-wex-addon-dev-css
|
|
3
|
+
Version: 6.0.74
|
|
4
|
+
Summary: Plugs a named CSS addon manager into the wex CLI kernel, serving as the registration entry point for CSS development tooling within the wex addon ecosystem
|
|
5
|
+
Author-Email: weeger <contact@wexample.com>
|
|
6
|
+
License: MIT
|
|
7
|
+
Classifier: Programming Language :: Python :: 3
|
|
8
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
9
|
+
Classifier: Operating System :: OS Independent
|
|
10
|
+
Requires-Python: >=3.10
|
|
11
|
+
Requires-Dist: attrs>=23.1.0
|
|
12
|
+
Requires-Dist: cattrs>=23.1.0
|
|
13
|
+
Requires-Dist: wexample-wex-addon-app>=30.0.0
|
|
14
|
+
Provides-Extra: dev
|
|
15
|
+
Requires-Dist: pytest; extra == "dev"
|
|
16
|
+
Requires-Dist: pytest-cov; extra == "dev"
|
|
17
|
+
Description-Content-Type: text/markdown
|
|
18
|
+
|
|
19
|
+
# wex_addon_dev_css
|
|
20
|
+
|
|
21
|
+
Version: 6.0.74
|
|
22
|
+
|
|
23
|
+
`wex_addon_dev_css` registers a `CssAddonManager` — a named subclass of `AbstractAddonManager` — into the wex CLI kernel, making it the entry point for CSS development tooling within the wex addon ecosystem. It carries no commands of its own; its role is to give the kernel a named CSS addon slot that other packages and addons can target. It is intended for developers working inside the wex ecosystem who need CSS tooling exposed through the CLI.
|
|
24
|
+
|
|
25
|
+
## Table of Contents
|
|
26
|
+
|
|
27
|
+
- [Installation](#installation)
|
|
28
|
+
- [Quickstart](#quickstart)
|
|
29
|
+
- [Tests](#tests)
|
|
30
|
+
- [Architecture](#architecture)
|
|
31
|
+
- [Integration in the Suite](#integration-in-the-suite)
|
|
32
|
+
- [Dependencies](#dependencies)
|
|
33
|
+
- [Versioning & Compatibility Policy](#versioning--compatibility-policy)
|
|
34
|
+
- [License](#license)
|
|
35
|
+
- [About us](#about-us)
|
|
36
|
+
- [Known Limitations & Roadmap](#known-limitations--roadmap)
|
|
37
|
+
- [Status & Compatibility](#status--compatibility)
|
|
38
|
+
- [Useful Links](#useful-links)
|
|
39
|
+
- [Migration Notes](#migration-notes)
|
|
40
|
+
|
|
41
|
+
## Installation
|
|
42
|
+
|
|
43
|
+
```bash
|
|
44
|
+
pip install wexample-wex-addon-dev-css
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Requires Python >=3.10.
|
|
48
|
+
|
|
49
|
+
## Quickstart
|
|
50
|
+
|
|
51
|
+
Install the package:
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
pip install wexample-wex-addon-dev-css
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
The public entry point is `CssAddonManager`, defined in src/wexample_wex_addon_dev_css/css_addon_manager.py:
|
|
58
|
+
|
|
59
|
+
```python
|
|
60
|
+
from wexample_wex_addon_dev_css.css_addon_manager import CssAddonManager
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
Pass it to the kernel's `setup()` call to register the CSS addon slot:
|
|
64
|
+
|
|
65
|
+
```python
|
|
66
|
+
from wexample_wex_core.common.kernel import Kernel
|
|
67
|
+
|
|
68
|
+
kernel = Kernel()
|
|
69
|
+
kernel.setup(addons=[CssAddonManager])
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
After `setup()` returns, the kernel holds a `css` addon entry (the name is derived from the class by stripping the `AddonManager` suffix). Other packages that target the CSS slot can then resolve it via `kernel.get_addons()["css"]`. The manager itself carries no commands; its presence in the addon list is the registration.
|
|
73
|
+
|
|
74
|
+
## Tests
|
|
75
|
+
|
|
76
|
+
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
77
|
+
|
|
78
|
+
### Installation
|
|
79
|
+
|
|
80
|
+
First, install the required testing dependencies:
|
|
81
|
+
```bash
|
|
82
|
+
.venv/bin/python -m pip install pytest pytest-cov
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
### Basic Usage
|
|
86
|
+
|
|
87
|
+
Run all tests with coverage:
|
|
88
|
+
```bash
|
|
89
|
+
.venv/bin/python -m pytest --cov --cov-report=html
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Common Commands
|
|
93
|
+
```bash
|
|
94
|
+
# Run tests with coverage for a specific module
|
|
95
|
+
.venv/bin/python -m pytest --cov=your_module
|
|
96
|
+
|
|
97
|
+
# Show which lines are not covered
|
|
98
|
+
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
99
|
+
|
|
100
|
+
# Generate an HTML coverage report
|
|
101
|
+
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
102
|
+
|
|
103
|
+
# Combine terminal and HTML reports
|
|
104
|
+
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
105
|
+
|
|
106
|
+
# Run specific test file with coverage
|
|
107
|
+
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
### Viewing HTML Reports
|
|
111
|
+
|
|
112
|
+
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
113
|
+
|
|
114
|
+
### Coverage Threshold
|
|
115
|
+
|
|
116
|
+
To enforce a minimum coverage percentage:
|
|
117
|
+
```bash
|
|
118
|
+
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
This will cause the test suite to fail if coverage drops below 80%.
|
|
122
|
+
|
|
123
|
+
## Architecture
|
|
124
|
+
|
|
125
|
+
The package contains one Python module under `src/wexample_wex_addon_dev_css/`. Its entire public surface is `CssAddonManager`, defined in src/wexample_wex_addon_dev_css/css_addon_manager.py.
|
|
126
|
+
|
|
127
|
+
### Parts
|
|
128
|
+
|
|
129
|
+
**`CssAddonManager`** subclasses `AbstractAddonManager` from `wexample_wex_core` and adds nothing — its body is `pass`. All behaviour comes from the base class.
|
|
130
|
+
|
|
131
|
+
**`AbstractAddonManager`** (in `wexample-wex-core`) carries the registration logic. It inherits from:
|
|
132
|
+
|
|
133
|
+
- `AbstractKernelChild` — gives the instance a reference to the kernel that owns it.
|
|
134
|
+
- `HasSnakeShortClassNameClassMixin` — derives the addon slot name by stripping the `AddonManager` suffix from the class name and snake-casing the result. `CssAddonManager` → `Css` → `css`.
|
|
135
|
+
- `WithWorkdirMixin` — sets the addon's workdir to the directory of the class file during `__attrs_post_init__`.
|
|
136
|
+
- `HasTwoStepInit` — enforces the two-phase `attrs` initialisation pattern the kernel uses for all its children.
|
|
137
|
+
|
|
138
|
+
The base class exposes hook methods (`get_command_resolver_classes`, `get_middlewares_classes`, `get_step_guard_classes`, `get_workdir_types`, etc.) that a richer addon would override. `CssAddonManager` inherits all of them and returns their defaults (empty lists/dicts).
|
|
139
|
+
|
|
140
|
+
### Registration path
|
|
141
|
+
|
|
142
|
+
1. A caller constructs a kernel and passes `CssAddonManager` in the `addons` list to `kernel.setup()`.
|
|
143
|
+
2. The kernel instantiates the class, triggering `__attrs_post_init__`, which calls `_init_workdir` with the directory containing src/wexample_wex_addon_dev_css/css_addon_manager.py as the entrypoint path.
|
|
144
|
+
3. The kernel indexes the instance under the key `css` (the result of `CssAddonManager.get_name()`).
|
|
145
|
+
4. Any downstream package that needs the CSS slot calls `kernel.get_addons()["css"]` to retrieve the manager.
|
|
146
|
+
|
|
147
|
+
The package itself issues no CLI commands and registers no resolvers. Its only job is to occupy the `css` slot so that other packages in the ecosystem have a stable, named target to extend or query.
|
|
148
|
+
|
|
149
|
+
### Package layout
|
|
150
|
+
|
|
151
|
+
```
|
|
152
|
+
src/
|
|
153
|
+
└── wexample_wex_addon_dev_css/
|
|
154
|
+
├── __init__.py # empty
|
|
155
|
+
├── py.typed # PEP 561 marker
|
|
156
|
+
└── css_addon_manager.py # CssAddonManager
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
The build backend is `pdm-backend`. `pyproject.toml` declares one runtime dependency group: `wexample-wex-addon-app`, which pulls in the wex-core base classes; plus `attrs` and `cattrs` for the attrs-based init pattern.
|
|
160
|
+
|
|
161
|
+
## Integration in the Suite
|
|
162
|
+
|
|
163
|
+
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
164
|
+
|
|
165
|
+
### Related Packages
|
|
166
|
+
|
|
167
|
+
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
168
|
+
|
|
169
|
+
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
170
|
+
|
|
171
|
+
## Dependencies
|
|
172
|
+
|
|
173
|
+
- attrs: >=23.1.0
|
|
174
|
+
- cattrs: >=23.1.0
|
|
175
|
+
- wexample-wex-addon-app: >=30.0.0
|
|
176
|
+
|
|
177
|
+
## Versioning & Compatibility Policy
|
|
178
|
+
|
|
179
|
+
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
180
|
+
|
|
181
|
+
- **MAJOR**: Breaking changes
|
|
182
|
+
- **MINOR**: New features, backward compatible
|
|
183
|
+
- **PATCH**: Bug fixes, backward compatible
|
|
184
|
+
|
|
185
|
+
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
186
|
+
|
|
187
|
+
## License
|
|
188
|
+
|
|
189
|
+
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
190
|
+
|
|
191
|
+
Free to use in both personal and commercial projects.
|
|
192
|
+
|
|
193
|
+
## About us
|
|
194
|
+
|
|
195
|
+
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
196
|
+
|
|
197
|
+
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
198
|
+
|
|
199
|
+
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
200
|
+
|
|
201
|
+
## Known Limitations & Roadmap
|
|
202
|
+
|
|
203
|
+
Current limitations and planned features are tracked in the GitHub issues.
|
|
204
|
+
|
|
205
|
+
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
206
|
+
|
|
207
|
+
## Status & Compatibility
|
|
208
|
+
|
|
209
|
+
**Maturity**: Production-ready
|
|
210
|
+
|
|
211
|
+
**Python Support**: >=3.10
|
|
212
|
+
|
|
213
|
+
**OS Support**: Linux, macOS, Windows
|
|
214
|
+
|
|
215
|
+
**Status**: Actively maintained
|
|
216
|
+
|
|
217
|
+
## Useful Links
|
|
218
|
+
|
|
219
|
+
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
220
|
+
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
221
|
+
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
222
|
+
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
223
|
+
- **PyPI**: [pypi.org/project/wexample-wex-addon-dev-css](https://pypi.org/project/wexample-wex-addon-dev-css/)
|
|
224
|
+
|
|
225
|
+
## Migration Notes
|
|
226
|
+
|
|
227
|
+
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
228
|
+
|
|
229
|
+
Breaking changes are clearly documented with upgrade paths and examples.
|
|
@@ -0,0 +1,211 @@
|
|
|
1
|
+
# wex_addon_dev_css
|
|
2
|
+
|
|
3
|
+
Version: 6.0.74
|
|
4
|
+
|
|
5
|
+
`wex_addon_dev_css` registers a `CssAddonManager` — a named subclass of `AbstractAddonManager` — into the wex CLI kernel, making it the entry point for CSS development tooling within the wex addon ecosystem. It carries no commands of its own; its role is to give the kernel a named CSS addon slot that other packages and addons can target. It is intended for developers working inside the wex ecosystem who need CSS tooling exposed through the CLI.
|
|
6
|
+
|
|
7
|
+
## Table of Contents
|
|
8
|
+
|
|
9
|
+
- [Installation](#installation)
|
|
10
|
+
- [Quickstart](#quickstart)
|
|
11
|
+
- [Tests](#tests)
|
|
12
|
+
- [Architecture](#architecture)
|
|
13
|
+
- [Integration in the Suite](#integration-in-the-suite)
|
|
14
|
+
- [Dependencies](#dependencies)
|
|
15
|
+
- [Versioning & Compatibility Policy](#versioning--compatibility-policy)
|
|
16
|
+
- [License](#license)
|
|
17
|
+
- [About us](#about-us)
|
|
18
|
+
- [Known Limitations & Roadmap](#known-limitations--roadmap)
|
|
19
|
+
- [Status & Compatibility](#status--compatibility)
|
|
20
|
+
- [Useful Links](#useful-links)
|
|
21
|
+
- [Migration Notes](#migration-notes)
|
|
22
|
+
|
|
23
|
+
## Installation
|
|
24
|
+
|
|
25
|
+
```bash
|
|
26
|
+
pip install wexample-wex-addon-dev-css
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
Requires Python >=3.10.
|
|
30
|
+
|
|
31
|
+
## Quickstart
|
|
32
|
+
|
|
33
|
+
Install the package:
|
|
34
|
+
|
|
35
|
+
```bash
|
|
36
|
+
pip install wexample-wex-addon-dev-css
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
The public entry point is `CssAddonManager`, defined in src/wexample_wex_addon_dev_css/css_addon_manager.py:
|
|
40
|
+
|
|
41
|
+
```python
|
|
42
|
+
from wexample_wex_addon_dev_css.css_addon_manager import CssAddonManager
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
Pass it to the kernel's `setup()` call to register the CSS addon slot:
|
|
46
|
+
|
|
47
|
+
```python
|
|
48
|
+
from wexample_wex_core.common.kernel import Kernel
|
|
49
|
+
|
|
50
|
+
kernel = Kernel()
|
|
51
|
+
kernel.setup(addons=[CssAddonManager])
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
After `setup()` returns, the kernel holds a `css` addon entry (the name is derived from the class by stripping the `AddonManager` suffix). Other packages that target the CSS slot can then resolve it via `kernel.get_addons()["css"]`. The manager itself carries no commands; its presence in the addon list is the registration.
|
|
55
|
+
|
|
56
|
+
## Tests
|
|
57
|
+
|
|
58
|
+
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
59
|
+
|
|
60
|
+
### Installation
|
|
61
|
+
|
|
62
|
+
First, install the required testing dependencies:
|
|
63
|
+
```bash
|
|
64
|
+
.venv/bin/python -m pip install pytest pytest-cov
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### Basic Usage
|
|
68
|
+
|
|
69
|
+
Run all tests with coverage:
|
|
70
|
+
```bash
|
|
71
|
+
.venv/bin/python -m pytest --cov --cov-report=html
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
### Common Commands
|
|
75
|
+
```bash
|
|
76
|
+
# Run tests with coverage for a specific module
|
|
77
|
+
.venv/bin/python -m pytest --cov=your_module
|
|
78
|
+
|
|
79
|
+
# Show which lines are not covered
|
|
80
|
+
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
81
|
+
|
|
82
|
+
# Generate an HTML coverage report
|
|
83
|
+
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
84
|
+
|
|
85
|
+
# Combine terminal and HTML reports
|
|
86
|
+
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
87
|
+
|
|
88
|
+
# Run specific test file with coverage
|
|
89
|
+
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Viewing HTML Reports
|
|
93
|
+
|
|
94
|
+
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
95
|
+
|
|
96
|
+
### Coverage Threshold
|
|
97
|
+
|
|
98
|
+
To enforce a minimum coverage percentage:
|
|
99
|
+
```bash
|
|
100
|
+
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
This will cause the test suite to fail if coverage drops below 80%.
|
|
104
|
+
|
|
105
|
+
## Architecture
|
|
106
|
+
|
|
107
|
+
The package contains one Python module under `src/wexample_wex_addon_dev_css/`. Its entire public surface is `CssAddonManager`, defined in src/wexample_wex_addon_dev_css/css_addon_manager.py.
|
|
108
|
+
|
|
109
|
+
### Parts
|
|
110
|
+
|
|
111
|
+
**`CssAddonManager`** subclasses `AbstractAddonManager` from `wexample_wex_core` and adds nothing — its body is `pass`. All behaviour comes from the base class.
|
|
112
|
+
|
|
113
|
+
**`AbstractAddonManager`** (in `wexample-wex-core`) carries the registration logic. It inherits from:
|
|
114
|
+
|
|
115
|
+
- `AbstractKernelChild` — gives the instance a reference to the kernel that owns it.
|
|
116
|
+
- `HasSnakeShortClassNameClassMixin` — derives the addon slot name by stripping the `AddonManager` suffix from the class name and snake-casing the result. `CssAddonManager` → `Css` → `css`.
|
|
117
|
+
- `WithWorkdirMixin` — sets the addon's workdir to the directory of the class file during `__attrs_post_init__`.
|
|
118
|
+
- `HasTwoStepInit` — enforces the two-phase `attrs` initialisation pattern the kernel uses for all its children.
|
|
119
|
+
|
|
120
|
+
The base class exposes hook methods (`get_command_resolver_classes`, `get_middlewares_classes`, `get_step_guard_classes`, `get_workdir_types`, etc.) that a richer addon would override. `CssAddonManager` inherits all of them and returns their defaults (empty lists/dicts).
|
|
121
|
+
|
|
122
|
+
### Registration path
|
|
123
|
+
|
|
124
|
+
1. A caller constructs a kernel and passes `CssAddonManager` in the `addons` list to `kernel.setup()`.
|
|
125
|
+
2. The kernel instantiates the class, triggering `__attrs_post_init__`, which calls `_init_workdir` with the directory containing src/wexample_wex_addon_dev_css/css_addon_manager.py as the entrypoint path.
|
|
126
|
+
3. The kernel indexes the instance under the key `css` (the result of `CssAddonManager.get_name()`).
|
|
127
|
+
4. Any downstream package that needs the CSS slot calls `kernel.get_addons()["css"]` to retrieve the manager.
|
|
128
|
+
|
|
129
|
+
The package itself issues no CLI commands and registers no resolvers. Its only job is to occupy the `css` slot so that other packages in the ecosystem have a stable, named target to extend or query.
|
|
130
|
+
|
|
131
|
+
### Package layout
|
|
132
|
+
|
|
133
|
+
```
|
|
134
|
+
src/
|
|
135
|
+
└── wexample_wex_addon_dev_css/
|
|
136
|
+
├── __init__.py # empty
|
|
137
|
+
├── py.typed # PEP 561 marker
|
|
138
|
+
└── css_addon_manager.py # CssAddonManager
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
The build backend is `pdm-backend`. `pyproject.toml` declares one runtime dependency group: `wexample-wex-addon-app`, which pulls in the wex-core base classes; plus `attrs` and `cattrs` for the attrs-based init pattern.
|
|
142
|
+
|
|
143
|
+
## Integration in the Suite
|
|
144
|
+
|
|
145
|
+
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
146
|
+
|
|
147
|
+
### Related Packages
|
|
148
|
+
|
|
149
|
+
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
150
|
+
|
|
151
|
+
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
152
|
+
|
|
153
|
+
## Dependencies
|
|
154
|
+
|
|
155
|
+
- attrs: >=23.1.0
|
|
156
|
+
- cattrs: >=23.1.0
|
|
157
|
+
- wexample-wex-addon-app: >=30.0.0
|
|
158
|
+
|
|
159
|
+
## Versioning & Compatibility Policy
|
|
160
|
+
|
|
161
|
+
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
162
|
+
|
|
163
|
+
- **MAJOR**: Breaking changes
|
|
164
|
+
- **MINOR**: New features, backward compatible
|
|
165
|
+
- **PATCH**: Bug fixes, backward compatible
|
|
166
|
+
|
|
167
|
+
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
168
|
+
|
|
169
|
+
## License
|
|
170
|
+
|
|
171
|
+
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
172
|
+
|
|
173
|
+
Free to use in both personal and commercial projects.
|
|
174
|
+
|
|
175
|
+
## About us
|
|
176
|
+
|
|
177
|
+
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
178
|
+
|
|
179
|
+
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
180
|
+
|
|
181
|
+
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
182
|
+
|
|
183
|
+
## Known Limitations & Roadmap
|
|
184
|
+
|
|
185
|
+
Current limitations and planned features are tracked in the GitHub issues.
|
|
186
|
+
|
|
187
|
+
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
188
|
+
|
|
189
|
+
## Status & Compatibility
|
|
190
|
+
|
|
191
|
+
**Maturity**: Production-ready
|
|
192
|
+
|
|
193
|
+
**Python Support**: >=3.10
|
|
194
|
+
|
|
195
|
+
**OS Support**: Linux, macOS, Windows
|
|
196
|
+
|
|
197
|
+
**Status**: Actively maintained
|
|
198
|
+
|
|
199
|
+
## Useful Links
|
|
200
|
+
|
|
201
|
+
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
202
|
+
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
203
|
+
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
204
|
+
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
205
|
+
- **PyPI**: [pypi.org/project/wexample-wex-addon-dev-css](https://pypi.org/project/wexample-wex-addon-dev-css/)
|
|
206
|
+
|
|
207
|
+
## Migration Notes
|
|
208
|
+
|
|
209
|
+
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
210
|
+
|
|
211
|
+
Breaking changes are clearly documented with upgrade paths and examples.
|
|
@@ -6,7 +6,8 @@ build-backend = "pdm.backend"
|
|
|
6
6
|
|
|
7
7
|
[project]
|
|
8
8
|
name = "wexample-wex-addon-dev-css"
|
|
9
|
-
version = "6.0.
|
|
9
|
+
version = "6.0.74"
|
|
10
|
+
description = "Plugs a named CSS addon manager into the wex CLI kernel, serving as the registration entry point for CSS development tooling within the wex addon ecosystem"
|
|
10
11
|
authors = [
|
|
11
12
|
{ name = "weeger", email = "contact@wexample.com" },
|
|
12
13
|
]
|
|
@@ -19,7 +20,7 @@ classifiers = [
|
|
|
19
20
|
dependencies = [
|
|
20
21
|
"attrs>=23.1.0",
|
|
21
22
|
"cattrs>=23.1.0",
|
|
22
|
-
"wexample-wex-addon-app>=
|
|
23
|
+
"wexample-wex-addon-app>=30.0.0",
|
|
23
24
|
]
|
|
24
25
|
|
|
25
26
|
[project.readme]
|
|
File without changes
|
|
@@ -1,459 +0,0 @@
|
|
|
1
|
-
Metadata-Version: 2.1
|
|
2
|
-
Name: wexample-wex-addon-dev-css
|
|
3
|
-
Version: 6.0.73
|
|
4
|
-
Author-Email: weeger <contact@wexample.com>
|
|
5
|
-
License: MIT
|
|
6
|
-
Classifier: Programming Language :: Python :: 3
|
|
7
|
-
Classifier: License :: OSI Approved :: MIT License
|
|
8
|
-
Classifier: Operating System :: OS Independent
|
|
9
|
-
Requires-Python: >=3.10
|
|
10
|
-
Requires-Dist: attrs>=23.1.0
|
|
11
|
-
Requires-Dist: cattrs>=23.1.0
|
|
12
|
-
Requires-Dist: wexample-wex-addon-app>=29.0.0
|
|
13
|
-
Provides-Extra: dev
|
|
14
|
-
Requires-Dist: pytest; extra == "dev"
|
|
15
|
-
Requires-Dist: pytest-cov; extra == "dev"
|
|
16
|
-
Description-Content-Type: text/markdown
|
|
17
|
-
|
|
18
|
-
# wex_addon_dev_css
|
|
19
|
-
|
|
20
|
-
Version: 6.0.73
|
|
21
|
-
|
|
22
|
-
## Table of Contents
|
|
23
|
-
|
|
24
|
-
- [Tests](#tests)
|
|
25
|
-
- [Suite Integration](#suite-integration)
|
|
26
|
-
- [Dependencies](#dependencies)
|
|
27
|
-
- [Versioning](#versioning)
|
|
28
|
-
- [License](#license)
|
|
29
|
-
- [Suite Integration](#suite-integration)
|
|
30
|
-
- [Suite Signature](#suite-signature)
|
|
31
|
-
- [Introduction](#introduction)
|
|
32
|
-
- [Roadmap](#roadmap)
|
|
33
|
-
- [Status Compatibility](#status-compatibility)
|
|
34
|
-
- [Useful Links](#useful-links)
|
|
35
|
-
- [Migration Notes](#migration-notes)
|
|
36
|
-
|
|
37
|
-
## Tests
|
|
38
|
-
|
|
39
|
-
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
40
|
-
|
|
41
|
-
### Installation
|
|
42
|
-
|
|
43
|
-
First, install the required testing dependencies:
|
|
44
|
-
```bash
|
|
45
|
-
.venv/bin/python -m pip install pytest pytest-cov
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
### Basic Usage
|
|
49
|
-
|
|
50
|
-
Run all tests with coverage:
|
|
51
|
-
```bash
|
|
52
|
-
.venv/bin/python -m pytest --cov --cov-report=html
|
|
53
|
-
```
|
|
54
|
-
|
|
55
|
-
### Common Commands
|
|
56
|
-
```bash
|
|
57
|
-
# Run tests with coverage for a specific module
|
|
58
|
-
.venv/bin/python -m pytest --cov=your_module
|
|
59
|
-
|
|
60
|
-
# Show which lines are not covered
|
|
61
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
62
|
-
|
|
63
|
-
# Generate an HTML coverage report
|
|
64
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
65
|
-
|
|
66
|
-
# Combine terminal and HTML reports
|
|
67
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
68
|
-
|
|
69
|
-
# Run specific test file with coverage
|
|
70
|
-
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
71
|
-
```
|
|
72
|
-
|
|
73
|
-
### Viewing HTML Reports
|
|
74
|
-
|
|
75
|
-
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
76
|
-
|
|
77
|
-
### Coverage Threshold
|
|
78
|
-
|
|
79
|
-
To enforce a minimum coverage percentage:
|
|
80
|
-
```bash
|
|
81
|
-
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
82
|
-
```
|
|
83
|
-
|
|
84
|
-
This will cause the test suite to fail if coverage drops below 80%.
|
|
85
|
-
|
|
86
|
-
## Integration in the Suite
|
|
87
|
-
|
|
88
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
89
|
-
|
|
90
|
-
### Related Packages
|
|
91
|
-
|
|
92
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
93
|
-
|
|
94
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
95
|
-
|
|
96
|
-
## Dependencies
|
|
97
|
-
|
|
98
|
-
- attrs: >=23.1.0
|
|
99
|
-
- cattrs: >=23.1.0
|
|
100
|
-
- wexample-wex-addon-app: >=29.0.0
|
|
101
|
-
|
|
102
|
-
## Versioning & Compatibility Policy
|
|
103
|
-
|
|
104
|
-
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
105
|
-
|
|
106
|
-
- **MAJOR**: Breaking changes
|
|
107
|
-
- **MINOR**: New features, backward compatible
|
|
108
|
-
- **PATCH**: Bug fixes, backward compatible
|
|
109
|
-
|
|
110
|
-
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
111
|
-
|
|
112
|
-
## License
|
|
113
|
-
|
|
114
|
-
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
115
|
-
|
|
116
|
-
Free to use in both personal and commercial projects.
|
|
117
|
-
|
|
118
|
-
## Integration in the Suite
|
|
119
|
-
|
|
120
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
121
|
-
|
|
122
|
-
### Related Packages
|
|
123
|
-
|
|
124
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
125
|
-
|
|
126
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
127
|
-
|
|
128
|
-
# About us
|
|
129
|
-
|
|
130
|
-
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
131
|
-
|
|
132
|
-
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
133
|
-
|
|
134
|
-
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
135
|
-
|
|
136
|
-
# wex_addon_dev_css
|
|
137
|
-
|
|
138
|
-
Version: 6.0.36
|
|
139
|
-
|
|
140
|
-
## Table of Contents
|
|
141
|
-
|
|
142
|
-
- [Tests](#tests)
|
|
143
|
-
- [Suite Integration](#suite-integration)
|
|
144
|
-
- [Dependencies](#dependencies)
|
|
145
|
-
- [Versioning](#versioning)
|
|
146
|
-
- [License](#license)
|
|
147
|
-
- [Suite Integration](#suite-integration)
|
|
148
|
-
- [Suite Signature](#suite-signature)
|
|
149
|
-
- [Introduction](#introduction)
|
|
150
|
-
- [Roadmap](#roadmap)
|
|
151
|
-
- [Status Compatibility](#status-compatibility)
|
|
152
|
-
- [Useful Links](#useful-links)
|
|
153
|
-
- [Migration Notes](#migration-notes)
|
|
154
|
-
|
|
155
|
-
## Tests
|
|
156
|
-
|
|
157
|
-
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
158
|
-
|
|
159
|
-
### Installation
|
|
160
|
-
|
|
161
|
-
First, install the required testing dependencies:
|
|
162
|
-
```bash
|
|
163
|
-
.venv/bin/python -m pip install pytest pytest-cov
|
|
164
|
-
```
|
|
165
|
-
|
|
166
|
-
### Basic Usage
|
|
167
|
-
|
|
168
|
-
Run all tests with coverage:
|
|
169
|
-
```bash
|
|
170
|
-
.venv/bin/python -m pytest --cov --cov-report=html
|
|
171
|
-
```
|
|
172
|
-
|
|
173
|
-
### Common Commands
|
|
174
|
-
```bash
|
|
175
|
-
# Run tests with coverage for a specific module
|
|
176
|
-
.venv/bin/python -m pytest --cov=your_module
|
|
177
|
-
|
|
178
|
-
# Show which lines are not covered
|
|
179
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
180
|
-
|
|
181
|
-
# Generate an HTML coverage report
|
|
182
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
183
|
-
|
|
184
|
-
# Combine terminal and HTML reports
|
|
185
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
186
|
-
|
|
187
|
-
# Run specific test file with coverage
|
|
188
|
-
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
189
|
-
```
|
|
190
|
-
|
|
191
|
-
### Viewing HTML Reports
|
|
192
|
-
|
|
193
|
-
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
194
|
-
|
|
195
|
-
### Coverage Threshold
|
|
196
|
-
|
|
197
|
-
To enforce a minimum coverage percentage:
|
|
198
|
-
```bash
|
|
199
|
-
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
200
|
-
```
|
|
201
|
-
|
|
202
|
-
This will cause the test suite to fail if coverage drops below 80%.
|
|
203
|
-
|
|
204
|
-
## Integration in the Suite
|
|
205
|
-
|
|
206
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
207
|
-
|
|
208
|
-
### Related Packages
|
|
209
|
-
|
|
210
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
211
|
-
|
|
212
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
213
|
-
|
|
214
|
-
## Dependencies
|
|
215
|
-
|
|
216
|
-
- attrs: >=23.1.0
|
|
217
|
-
- cattrs: >=23.1.0
|
|
218
|
-
- wexample-wex-addon-app: >=16.6.0
|
|
219
|
-
|
|
220
|
-
## Versioning & Compatibility Policy
|
|
221
|
-
|
|
222
|
-
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
223
|
-
|
|
224
|
-
- **MAJOR**: Breaking changes
|
|
225
|
-
- **MINOR**: New features, backward compatible
|
|
226
|
-
- **PATCH**: Bug fixes, backward compatible
|
|
227
|
-
|
|
228
|
-
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
229
|
-
|
|
230
|
-
## License
|
|
231
|
-
|
|
232
|
-
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
233
|
-
|
|
234
|
-
Free to use in both personal and commercial projects.
|
|
235
|
-
|
|
236
|
-
## Integration in the Suite
|
|
237
|
-
|
|
238
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
239
|
-
|
|
240
|
-
### Related Packages
|
|
241
|
-
|
|
242
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
243
|
-
|
|
244
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
245
|
-
|
|
246
|
-
# About us
|
|
247
|
-
|
|
248
|
-
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
249
|
-
|
|
250
|
-
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
251
|
-
|
|
252
|
-
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
253
|
-
|
|
254
|
-
# wex_addon_dev_css
|
|
255
|
-
|
|
256
|
-
Version: 0.0.20
|
|
257
|
-
|
|
258
|
-
## Table of Contents
|
|
259
|
-
|
|
260
|
-
- [Tests](#tests)
|
|
261
|
-
- [Suite Integration](#suite-integration)
|
|
262
|
-
- [Dependencies](#dependencies)
|
|
263
|
-
- [Versioning](#versioning)
|
|
264
|
-
- [License](#license)
|
|
265
|
-
- [Suite Integration](#suite-integration)
|
|
266
|
-
- [Suite Signature](#suite-signature)
|
|
267
|
-
- [Roadmap](#roadmap)
|
|
268
|
-
- [Status Compatibility](#status-compatibility)
|
|
269
|
-
- [Useful Links](#useful-links)
|
|
270
|
-
- [Migration Notes](#migration-notes)
|
|
271
|
-
|
|
272
|
-
## Tests
|
|
273
|
-
|
|
274
|
-
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
275
|
-
|
|
276
|
-
### Installation
|
|
277
|
-
|
|
278
|
-
First, install the required testing dependencies:
|
|
279
|
-
```bash
|
|
280
|
-
.venv/bin/python -m pip install pytest pytest-cov
|
|
281
|
-
```
|
|
282
|
-
|
|
283
|
-
### Basic Usage
|
|
284
|
-
|
|
285
|
-
Run all tests with coverage:
|
|
286
|
-
```bash
|
|
287
|
-
.venv/bin/python -m pytest --cov --cov-report=html
|
|
288
|
-
```
|
|
289
|
-
|
|
290
|
-
### Common Commands
|
|
291
|
-
```bash
|
|
292
|
-
# Run tests with coverage for a specific module
|
|
293
|
-
.venv/bin/python -m pytest --cov=your_module
|
|
294
|
-
|
|
295
|
-
# Show which lines are not covered
|
|
296
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
297
|
-
|
|
298
|
-
# Generate an HTML coverage report
|
|
299
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
300
|
-
|
|
301
|
-
# Combine terminal and HTML reports
|
|
302
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
303
|
-
|
|
304
|
-
# Run specific test file with coverage
|
|
305
|
-
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
306
|
-
```
|
|
307
|
-
|
|
308
|
-
### Viewing HTML Reports
|
|
309
|
-
|
|
310
|
-
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
311
|
-
|
|
312
|
-
### Coverage Threshold
|
|
313
|
-
|
|
314
|
-
To enforce a minimum coverage percentage:
|
|
315
|
-
```bash
|
|
316
|
-
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
317
|
-
```
|
|
318
|
-
|
|
319
|
-
This will cause the test suite to fail if coverage drops below 80%.
|
|
320
|
-
|
|
321
|
-
## Integration in the Suite
|
|
322
|
-
|
|
323
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
324
|
-
|
|
325
|
-
### Related Packages
|
|
326
|
-
|
|
327
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
328
|
-
|
|
329
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
330
|
-
|
|
331
|
-
## Dependencies
|
|
332
|
-
|
|
333
|
-
- attrs: >=23.1.0
|
|
334
|
-
- cattrs: >=23.1.0
|
|
335
|
-
- wexample-wex-addon-app: >=1.1.0
|
|
336
|
-
|
|
337
|
-
## Versioning & Compatibility Policy
|
|
338
|
-
|
|
339
|
-
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
340
|
-
|
|
341
|
-
- **MAJOR**: Breaking changes
|
|
342
|
-
- **MINOR**: New features, backward compatible
|
|
343
|
-
- **PATCH**: Bug fixes, backward compatible
|
|
344
|
-
|
|
345
|
-
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
346
|
-
|
|
347
|
-
## License
|
|
348
|
-
|
|
349
|
-
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
350
|
-
|
|
351
|
-
Free to use in both personal and commercial projects.
|
|
352
|
-
|
|
353
|
-
## Integration in the Suite
|
|
354
|
-
|
|
355
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
356
|
-
|
|
357
|
-
### Related Packages
|
|
358
|
-
|
|
359
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
360
|
-
|
|
361
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
362
|
-
|
|
363
|
-
# About us
|
|
364
|
-
|
|
365
|
-
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
366
|
-
|
|
367
|
-
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
368
|
-
|
|
369
|
-
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
370
|
-
|
|
371
|
-
## Known Limitations & Roadmap
|
|
372
|
-
|
|
373
|
-
Current limitations and planned features are tracked in the GitHub issues.
|
|
374
|
-
|
|
375
|
-
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
376
|
-
|
|
377
|
-
## Status & Compatibility
|
|
378
|
-
|
|
379
|
-
**Maturity**: Production-ready
|
|
380
|
-
|
|
381
|
-
**Python Support**: >=3.10
|
|
382
|
-
|
|
383
|
-
**OS Support**: Linux, macOS, Windows
|
|
384
|
-
|
|
385
|
-
**Status**: Actively maintained
|
|
386
|
-
|
|
387
|
-
## Useful Links
|
|
388
|
-
|
|
389
|
-
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
390
|
-
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
391
|
-
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
392
|
-
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
393
|
-
- **PyPI**: [pypi.org/project/wex_addon_dev_css](https://pypi.org/project/wex_addon_dev_css/)
|
|
394
|
-
|
|
395
|
-
## Migration Notes
|
|
396
|
-
|
|
397
|
-
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
398
|
-
|
|
399
|
-
Breaking changes are clearly documented with upgrade paths and examples.
|
|
400
|
-
|
|
401
|
-
## Known Limitations & Roadmap
|
|
402
|
-
|
|
403
|
-
Current limitations and planned features are tracked in the GitHub issues.
|
|
404
|
-
|
|
405
|
-
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
406
|
-
|
|
407
|
-
## Status & Compatibility
|
|
408
|
-
|
|
409
|
-
**Maturity**: Production-ready
|
|
410
|
-
|
|
411
|
-
**Python Support**: >=3.10
|
|
412
|
-
|
|
413
|
-
**OS Support**: Linux, macOS, Windows
|
|
414
|
-
|
|
415
|
-
**Status**: Actively maintained
|
|
416
|
-
|
|
417
|
-
## Useful Links
|
|
418
|
-
|
|
419
|
-
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
420
|
-
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
421
|
-
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
422
|
-
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
423
|
-
- **PyPI**: [pypi.org/project/wex_addon_dev_css](https://pypi.org/project/wex_addon_dev_css/)
|
|
424
|
-
|
|
425
|
-
## Migration Notes
|
|
426
|
-
|
|
427
|
-
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
428
|
-
|
|
429
|
-
Breaking changes are clearly documented with upgrade paths and examples.
|
|
430
|
-
|
|
431
|
-
## Known Limitations & Roadmap
|
|
432
|
-
|
|
433
|
-
Current limitations and planned features are tracked in the GitHub issues.
|
|
434
|
-
|
|
435
|
-
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
436
|
-
|
|
437
|
-
## Status & Compatibility
|
|
438
|
-
|
|
439
|
-
**Maturity**: Production-ready
|
|
440
|
-
|
|
441
|
-
**Python Support**: >=3.10
|
|
442
|
-
|
|
443
|
-
**OS Support**: Linux, macOS, Windows
|
|
444
|
-
|
|
445
|
-
**Status**: Actively maintained
|
|
446
|
-
|
|
447
|
-
## Useful Links
|
|
448
|
-
|
|
449
|
-
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
450
|
-
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
451
|
-
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
452
|
-
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
453
|
-
- **PyPI**: [pypi.org/project/wex_addon_dev_css](https://pypi.org/project/wex_addon_dev_css/)
|
|
454
|
-
|
|
455
|
-
## Migration Notes
|
|
456
|
-
|
|
457
|
-
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
458
|
-
|
|
459
|
-
Breaking changes are clearly documented with upgrade paths and examples.
|
|
@@ -1,442 +0,0 @@
|
|
|
1
|
-
# wex_addon_dev_css
|
|
2
|
-
|
|
3
|
-
Version: 6.0.73
|
|
4
|
-
|
|
5
|
-
## Table of Contents
|
|
6
|
-
|
|
7
|
-
- [Tests](#tests)
|
|
8
|
-
- [Suite Integration](#suite-integration)
|
|
9
|
-
- [Dependencies](#dependencies)
|
|
10
|
-
- [Versioning](#versioning)
|
|
11
|
-
- [License](#license)
|
|
12
|
-
- [Suite Integration](#suite-integration)
|
|
13
|
-
- [Suite Signature](#suite-signature)
|
|
14
|
-
- [Introduction](#introduction)
|
|
15
|
-
- [Roadmap](#roadmap)
|
|
16
|
-
- [Status Compatibility](#status-compatibility)
|
|
17
|
-
- [Useful Links](#useful-links)
|
|
18
|
-
- [Migration Notes](#migration-notes)
|
|
19
|
-
|
|
20
|
-
## Tests
|
|
21
|
-
|
|
22
|
-
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
23
|
-
|
|
24
|
-
### Installation
|
|
25
|
-
|
|
26
|
-
First, install the required testing dependencies:
|
|
27
|
-
```bash
|
|
28
|
-
.venv/bin/python -m pip install pytest pytest-cov
|
|
29
|
-
```
|
|
30
|
-
|
|
31
|
-
### Basic Usage
|
|
32
|
-
|
|
33
|
-
Run all tests with coverage:
|
|
34
|
-
```bash
|
|
35
|
-
.venv/bin/python -m pytest --cov --cov-report=html
|
|
36
|
-
```
|
|
37
|
-
|
|
38
|
-
### Common Commands
|
|
39
|
-
```bash
|
|
40
|
-
# Run tests with coverage for a specific module
|
|
41
|
-
.venv/bin/python -m pytest --cov=your_module
|
|
42
|
-
|
|
43
|
-
# Show which lines are not covered
|
|
44
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
45
|
-
|
|
46
|
-
# Generate an HTML coverage report
|
|
47
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
48
|
-
|
|
49
|
-
# Combine terminal and HTML reports
|
|
50
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
51
|
-
|
|
52
|
-
# Run specific test file with coverage
|
|
53
|
-
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
54
|
-
```
|
|
55
|
-
|
|
56
|
-
### Viewing HTML Reports
|
|
57
|
-
|
|
58
|
-
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
59
|
-
|
|
60
|
-
### Coverage Threshold
|
|
61
|
-
|
|
62
|
-
To enforce a minimum coverage percentage:
|
|
63
|
-
```bash
|
|
64
|
-
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
This will cause the test suite to fail if coverage drops below 80%.
|
|
68
|
-
|
|
69
|
-
## Integration in the Suite
|
|
70
|
-
|
|
71
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
72
|
-
|
|
73
|
-
### Related Packages
|
|
74
|
-
|
|
75
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
76
|
-
|
|
77
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
78
|
-
|
|
79
|
-
## Dependencies
|
|
80
|
-
|
|
81
|
-
- attrs: >=23.1.0
|
|
82
|
-
- cattrs: >=23.1.0
|
|
83
|
-
- wexample-wex-addon-app: >=29.0.0
|
|
84
|
-
|
|
85
|
-
## Versioning & Compatibility Policy
|
|
86
|
-
|
|
87
|
-
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
88
|
-
|
|
89
|
-
- **MAJOR**: Breaking changes
|
|
90
|
-
- **MINOR**: New features, backward compatible
|
|
91
|
-
- **PATCH**: Bug fixes, backward compatible
|
|
92
|
-
|
|
93
|
-
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
94
|
-
|
|
95
|
-
## License
|
|
96
|
-
|
|
97
|
-
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
98
|
-
|
|
99
|
-
Free to use in both personal and commercial projects.
|
|
100
|
-
|
|
101
|
-
## Integration in the Suite
|
|
102
|
-
|
|
103
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
104
|
-
|
|
105
|
-
### Related Packages
|
|
106
|
-
|
|
107
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
108
|
-
|
|
109
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
110
|
-
|
|
111
|
-
# About us
|
|
112
|
-
|
|
113
|
-
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
114
|
-
|
|
115
|
-
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
116
|
-
|
|
117
|
-
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
118
|
-
|
|
119
|
-
# wex_addon_dev_css
|
|
120
|
-
|
|
121
|
-
Version: 6.0.36
|
|
122
|
-
|
|
123
|
-
## Table of Contents
|
|
124
|
-
|
|
125
|
-
- [Tests](#tests)
|
|
126
|
-
- [Suite Integration](#suite-integration)
|
|
127
|
-
- [Dependencies](#dependencies)
|
|
128
|
-
- [Versioning](#versioning)
|
|
129
|
-
- [License](#license)
|
|
130
|
-
- [Suite Integration](#suite-integration)
|
|
131
|
-
- [Suite Signature](#suite-signature)
|
|
132
|
-
- [Introduction](#introduction)
|
|
133
|
-
- [Roadmap](#roadmap)
|
|
134
|
-
- [Status Compatibility](#status-compatibility)
|
|
135
|
-
- [Useful Links](#useful-links)
|
|
136
|
-
- [Migration Notes](#migration-notes)
|
|
137
|
-
|
|
138
|
-
## Tests
|
|
139
|
-
|
|
140
|
-
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
141
|
-
|
|
142
|
-
### Installation
|
|
143
|
-
|
|
144
|
-
First, install the required testing dependencies:
|
|
145
|
-
```bash
|
|
146
|
-
.venv/bin/python -m pip install pytest pytest-cov
|
|
147
|
-
```
|
|
148
|
-
|
|
149
|
-
### Basic Usage
|
|
150
|
-
|
|
151
|
-
Run all tests with coverage:
|
|
152
|
-
```bash
|
|
153
|
-
.venv/bin/python -m pytest --cov --cov-report=html
|
|
154
|
-
```
|
|
155
|
-
|
|
156
|
-
### Common Commands
|
|
157
|
-
```bash
|
|
158
|
-
# Run tests with coverage for a specific module
|
|
159
|
-
.venv/bin/python -m pytest --cov=your_module
|
|
160
|
-
|
|
161
|
-
# Show which lines are not covered
|
|
162
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
163
|
-
|
|
164
|
-
# Generate an HTML coverage report
|
|
165
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
166
|
-
|
|
167
|
-
# Combine terminal and HTML reports
|
|
168
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
169
|
-
|
|
170
|
-
# Run specific test file with coverage
|
|
171
|
-
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
172
|
-
```
|
|
173
|
-
|
|
174
|
-
### Viewing HTML Reports
|
|
175
|
-
|
|
176
|
-
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
177
|
-
|
|
178
|
-
### Coverage Threshold
|
|
179
|
-
|
|
180
|
-
To enforce a minimum coverage percentage:
|
|
181
|
-
```bash
|
|
182
|
-
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
183
|
-
```
|
|
184
|
-
|
|
185
|
-
This will cause the test suite to fail if coverage drops below 80%.
|
|
186
|
-
|
|
187
|
-
## Integration in the Suite
|
|
188
|
-
|
|
189
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
190
|
-
|
|
191
|
-
### Related Packages
|
|
192
|
-
|
|
193
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
194
|
-
|
|
195
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
196
|
-
|
|
197
|
-
## Dependencies
|
|
198
|
-
|
|
199
|
-
- attrs: >=23.1.0
|
|
200
|
-
- cattrs: >=23.1.0
|
|
201
|
-
- wexample-wex-addon-app: >=16.6.0
|
|
202
|
-
|
|
203
|
-
## Versioning & Compatibility Policy
|
|
204
|
-
|
|
205
|
-
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
206
|
-
|
|
207
|
-
- **MAJOR**: Breaking changes
|
|
208
|
-
- **MINOR**: New features, backward compatible
|
|
209
|
-
- **PATCH**: Bug fixes, backward compatible
|
|
210
|
-
|
|
211
|
-
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
212
|
-
|
|
213
|
-
## License
|
|
214
|
-
|
|
215
|
-
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
216
|
-
|
|
217
|
-
Free to use in both personal and commercial projects.
|
|
218
|
-
|
|
219
|
-
## Integration in the Suite
|
|
220
|
-
|
|
221
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
222
|
-
|
|
223
|
-
### Related Packages
|
|
224
|
-
|
|
225
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
226
|
-
|
|
227
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
228
|
-
|
|
229
|
-
# About us
|
|
230
|
-
|
|
231
|
-
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
232
|
-
|
|
233
|
-
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
234
|
-
|
|
235
|
-
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
236
|
-
|
|
237
|
-
# wex_addon_dev_css
|
|
238
|
-
|
|
239
|
-
Version: 0.0.20
|
|
240
|
-
|
|
241
|
-
## Table of Contents
|
|
242
|
-
|
|
243
|
-
- [Tests](#tests)
|
|
244
|
-
- [Suite Integration](#suite-integration)
|
|
245
|
-
- [Dependencies](#dependencies)
|
|
246
|
-
- [Versioning](#versioning)
|
|
247
|
-
- [License](#license)
|
|
248
|
-
- [Suite Integration](#suite-integration)
|
|
249
|
-
- [Suite Signature](#suite-signature)
|
|
250
|
-
- [Roadmap](#roadmap)
|
|
251
|
-
- [Status Compatibility](#status-compatibility)
|
|
252
|
-
- [Useful Links](#useful-links)
|
|
253
|
-
- [Migration Notes](#migration-notes)
|
|
254
|
-
|
|
255
|
-
## Tests
|
|
256
|
-
|
|
257
|
-
This project uses `pytest` for testing and `pytest-cov` for code coverage analysis.
|
|
258
|
-
|
|
259
|
-
### Installation
|
|
260
|
-
|
|
261
|
-
First, install the required testing dependencies:
|
|
262
|
-
```bash
|
|
263
|
-
.venv/bin/python -m pip install pytest pytest-cov
|
|
264
|
-
```
|
|
265
|
-
|
|
266
|
-
### Basic Usage
|
|
267
|
-
|
|
268
|
-
Run all tests with coverage:
|
|
269
|
-
```bash
|
|
270
|
-
.venv/bin/python -m pytest --cov --cov-report=html
|
|
271
|
-
```
|
|
272
|
-
|
|
273
|
-
### Common Commands
|
|
274
|
-
```bash
|
|
275
|
-
# Run tests with coverage for a specific module
|
|
276
|
-
.venv/bin/python -m pytest --cov=your_module
|
|
277
|
-
|
|
278
|
-
# Show which lines are not covered
|
|
279
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing
|
|
280
|
-
|
|
281
|
-
# Generate an HTML coverage report
|
|
282
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=html
|
|
283
|
-
|
|
284
|
-
# Combine terminal and HTML reports
|
|
285
|
-
.venv/bin/python -m pytest --cov=your_module --cov-report=term-missing --cov-report=html
|
|
286
|
-
|
|
287
|
-
# Run specific test file with coverage
|
|
288
|
-
.venv/bin/python -m pytest tests/test_file.py --cov=your_module --cov-report=term-missing
|
|
289
|
-
```
|
|
290
|
-
|
|
291
|
-
### Viewing HTML Reports
|
|
292
|
-
|
|
293
|
-
After generating an HTML report, open `htmlcov/index.html` in your browser to view detailed line-by-line coverage information.
|
|
294
|
-
|
|
295
|
-
### Coverage Threshold
|
|
296
|
-
|
|
297
|
-
To enforce a minimum coverage percentage:
|
|
298
|
-
```bash
|
|
299
|
-
.venv/bin/python -m pytest --cov=your_module --cov-fail-under=80
|
|
300
|
-
```
|
|
301
|
-
|
|
302
|
-
This will cause the test suite to fail if coverage drops below 80%.
|
|
303
|
-
|
|
304
|
-
## Integration in the Suite
|
|
305
|
-
|
|
306
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
307
|
-
|
|
308
|
-
### Related Packages
|
|
309
|
-
|
|
310
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
311
|
-
|
|
312
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
313
|
-
|
|
314
|
-
## Dependencies
|
|
315
|
-
|
|
316
|
-
- attrs: >=23.1.0
|
|
317
|
-
- cattrs: >=23.1.0
|
|
318
|
-
- wexample-wex-addon-app: >=1.1.0
|
|
319
|
-
|
|
320
|
-
## Versioning & Compatibility Policy
|
|
321
|
-
|
|
322
|
-
Wexample packages follow **Semantic Versioning** (SemVer):
|
|
323
|
-
|
|
324
|
-
- **MAJOR**: Breaking changes
|
|
325
|
-
- **MINOR**: New features, backward compatible
|
|
326
|
-
- **PATCH**: Bug fixes, backward compatible
|
|
327
|
-
|
|
328
|
-
We maintain backward compatibility within major versions and provide clear migration guides for breaking changes.
|
|
329
|
-
|
|
330
|
-
## License
|
|
331
|
-
|
|
332
|
-
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
|
333
|
-
|
|
334
|
-
Free to use in both personal and commercial projects.
|
|
335
|
-
|
|
336
|
-
## Integration in the Suite
|
|
337
|
-
|
|
338
|
-
This package is part of the Wexample Suite — a collection of high-quality, modular tools designed to work seamlessly together across multiple languages and environments.
|
|
339
|
-
|
|
340
|
-
### Related Packages
|
|
341
|
-
|
|
342
|
-
The suite includes packages for configuration management, file handling, prompts, and more. Each package can be used independently or as part of the integrated suite.
|
|
343
|
-
|
|
344
|
-
Visit the [Wexample Suite documentation](https://docs.wexample.com) for the complete package ecosystem.
|
|
345
|
-
|
|
346
|
-
# About us
|
|
347
|
-
|
|
348
|
-
[Wexample](https://wexample.com) stands as a cornerstone of the digital ecosystem — a collective of seasoned engineers, researchers, and creators driven by a relentless pursuit of technological excellence. More than a media platform, it has grown into a vibrant community where innovation meets craftsmanship, and where every line of code reflects a commitment to clarity, durability, and shared intelligence.
|
|
349
|
-
|
|
350
|
-
This packages suite embodies this spirit. Trusted by professionals and enthusiasts alike, it delivers a consistent, high-quality foundation for modern development — open, elegant, and battle-tested. Its reputation is built on years of collaboration, refinement, and rigorous attention to detail, making it a natural choice for those who demand both robustness and beauty in their tools.
|
|
351
|
-
|
|
352
|
-
Wexample cultivates a culture of mastery. Each package, each contribution carries the mark of a community that values precision, ethics, and innovation — a community proud to shape the future of digital craftsmanship.
|
|
353
|
-
|
|
354
|
-
## Known Limitations & Roadmap
|
|
355
|
-
|
|
356
|
-
Current limitations and planned features are tracked in the GitHub issues.
|
|
357
|
-
|
|
358
|
-
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
359
|
-
|
|
360
|
-
## Status & Compatibility
|
|
361
|
-
|
|
362
|
-
**Maturity**: Production-ready
|
|
363
|
-
|
|
364
|
-
**Python Support**: >=3.10
|
|
365
|
-
|
|
366
|
-
**OS Support**: Linux, macOS, Windows
|
|
367
|
-
|
|
368
|
-
**Status**: Actively maintained
|
|
369
|
-
|
|
370
|
-
## Useful Links
|
|
371
|
-
|
|
372
|
-
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
373
|
-
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
374
|
-
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
375
|
-
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
376
|
-
- **PyPI**: [pypi.org/project/wex_addon_dev_css](https://pypi.org/project/wex_addon_dev_css/)
|
|
377
|
-
|
|
378
|
-
## Migration Notes
|
|
379
|
-
|
|
380
|
-
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
381
|
-
|
|
382
|
-
Breaking changes are clearly documented with upgrade paths and examples.
|
|
383
|
-
|
|
384
|
-
## Known Limitations & Roadmap
|
|
385
|
-
|
|
386
|
-
Current limitations and planned features are tracked in the GitHub issues.
|
|
387
|
-
|
|
388
|
-
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
389
|
-
|
|
390
|
-
## Status & Compatibility
|
|
391
|
-
|
|
392
|
-
**Maturity**: Production-ready
|
|
393
|
-
|
|
394
|
-
**Python Support**: >=3.10
|
|
395
|
-
|
|
396
|
-
**OS Support**: Linux, macOS, Windows
|
|
397
|
-
|
|
398
|
-
**Status**: Actively maintained
|
|
399
|
-
|
|
400
|
-
## Useful Links
|
|
401
|
-
|
|
402
|
-
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
403
|
-
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
404
|
-
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
405
|
-
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
406
|
-
- **PyPI**: [pypi.org/project/wex_addon_dev_css](https://pypi.org/project/wex_addon_dev_css/)
|
|
407
|
-
|
|
408
|
-
## Migration Notes
|
|
409
|
-
|
|
410
|
-
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
411
|
-
|
|
412
|
-
Breaking changes are clearly documented with upgrade paths and examples.
|
|
413
|
-
|
|
414
|
-
## Known Limitations & Roadmap
|
|
415
|
-
|
|
416
|
-
Current limitations and planned features are tracked in the GitHub issues.
|
|
417
|
-
|
|
418
|
-
See the [project roadmap](https://github.com/wexample/python-wex_addon_dev_css/issues) for upcoming features and improvements.
|
|
419
|
-
|
|
420
|
-
## Status & Compatibility
|
|
421
|
-
|
|
422
|
-
**Maturity**: Production-ready
|
|
423
|
-
|
|
424
|
-
**Python Support**: >=3.10
|
|
425
|
-
|
|
426
|
-
**OS Support**: Linux, macOS, Windows
|
|
427
|
-
|
|
428
|
-
**Status**: Actively maintained
|
|
429
|
-
|
|
430
|
-
## Useful Links
|
|
431
|
-
|
|
432
|
-
- **Homepage**: https://github.com/wexample/python-wex-addon-dev-css
|
|
433
|
-
- **Documentation**: [docs.wexample.com](https://docs.wexample.com)
|
|
434
|
-
- **Issue Tracker**: https://github.com/wexample/python-wex-addon-dev-css/issues
|
|
435
|
-
- **Discussions**: https://github.com/wexample/python-wex-addon-dev-css/discussions
|
|
436
|
-
- **PyPI**: [pypi.org/project/wex_addon_dev_css](https://pypi.org/project/wex_addon_dev_css/)
|
|
437
|
-
|
|
438
|
-
## Migration Notes
|
|
439
|
-
|
|
440
|
-
When upgrading between major versions, refer to the migration guides in the documentation.
|
|
441
|
-
|
|
442
|
-
Breaking changes are clearly documented with upgrade paths and examples.
|
|
File without changes
|
|
File without changes
|
|
File without changes
|