Htmltypeprovider
C 62 completed
Other
unknown / fsharp · tiny
23
Files
1,240
LOC
0
Frameworks
3
Languages
Pipeline State
completedRun ID
#960378Phase
doneProgress
0%Started
2026-04-15 08:43:07Finished
2026-04-15 08:43:07LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
35.47Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:24Deduplication group #48996
Member of a group with 20 similar repo(s) — canonical #535117 view group →
All rows above produced by Repobility · https://repobility.com
AI Prompt
Create an F# type provider that can parse HTML templates containing `${HoleName}` placeholders and generate strongly-typed builder APIs. I need it to be inspired by Bolero but must output plain `string` via `StringBuilder` without any runtime framework dependencies. The system should support inline HTML and file-based templates, and the API must allow setting values for holes found in text content, single attributes, mixed attributes, and full attributes. Please include the builder methods like `.HoleName(value)`, `.Elt()`, and `.Render()`, along with the `Node` and `Attr` modules for building complex structures.
fsharp html templating string builder api web-component
Generated by gemma4:latest
Catalog Information
Create an F# type provider that can parse HTML templates containing ${HoleName} placeholders and generate strongly-typed builder APIs. I need it to be inspired by Bolero but must output plain string via StringBuilder without any runtime framework dependencies. The system should support inline HTML and file-based templates, and the API must allow setting values for holes found in text content, single attributes, mixed attributes, and full attributes. Please include the builder methods like
Tags
fsharp html templating string builder api web-component
Quality Score
C
61.7/100
Structure
49
Code Quality
93
Documentation
46
Testing
0
Practices
78
Security
100
Dependencies
50
Strengths
- Consistent naming conventions (PascalCase)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
