nix to json schema coverage #626
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#195 NixOS modules' options exposed
fediversity/fediversity
#627 expose applications' configuration options
fediversity/fediversity
#331 pydantic enum warning: Expected
enum but got str
fediversity/fediversity
Reference
fediversity/fediversity#626
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a Fediversity maintainer,
I want our converter from nix option modules to JSON schemas to cover further Nix types,
so that we may expose more NixOS service modules through Fediversity.
implementation notes
builds upon existing module (from #285) converting nix option modules to JSON schemas.
ways to expand on that include:
$defsattrTag-used in contracts implementationenumbut gotstr