Bricks: platform allow-list and per-platform NuGet in brick manifests
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- build-system, desktop
Research direction
Start with Gaya/Gaya.Packages/PackageManifest.cs and docs/bricks/package.schema.json, then trace BuildProfiles.ShippingBricks and CsProjectGenerator.AddBrickPackages to see how brick manifests and platform profiles are used. Check dependency #236 and the platform roadmap in #100 for context on platform naming; done means platform filtering, per-platform NuGet entries, an early error naming unsupported bricks, updated schema and docs, and tests, with desktop export unchanged.
Written by the indexing model from the issue text.
Description
Current State
Brick manifests (Gaya/Gaya.Packages/PackageManifest.cs, docs/bricks/package.schema.json) have one nuget map and client/server/editor flags, but no platform constraint. The UI brick lists desktop-only SkiaSharp natives and the vulkan brick lists GLFW; BuildProfiles.ShippingBricks filters only Client vs Server.
Tasks
- Add a
platformsallow-list (absent = any platform) - Add per-platform NuGet entries (decide naming)
-
ShippingBricksandCsProjectGenerator.AddBrickPackageshonor the profile's platform - Export fails early naming the unsupported brick
- Update the schema and brick docs
Acceptance Criteria
- Tests for platform filtering and the failure message
- Desktop export unchanged
Related
- Android plan task A12 · seniority Mid · mergeable now (.NET 10)
- Depends on: #236
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:build c:editor p:medium size:XL t:feature
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
c:build p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
c:build c:ui p:low size:L t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
c:assets c:build p:low size:S t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
bug misleading tooling trivial
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Docs example projects pinned to a literal library version instead of 3.*Possibly taken @DaveSkender claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facioquo/stock-indicators-dotnet#2372 ·
Maintainers usually reply within 1 day
-
[Docs] officecli-docx SKILL.md still describes `\n` as a soft line break after #262Possibly taken @giprime claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Facepunch/sbox-public#12097 ·
Maintainers usually reply within 2 days