expose JSON schema for inspection #351
No reviewers
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
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
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
2 participants
fricklerhandwerk
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fediversity/fediversity!351
Loading…
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:expose-json-schema"
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?
intending to document more about how our schemas work, i found our code currently buries this somewhere in
/nix/store.this change exposes that generated file in the project structure as well, facilitating inspection of our data schema in this more generic format.
@ -15,3 +15,3 @@fileset = intersection (gitTracked ../../.) ../src;};pyproject = with lib; fromTOML pyproject-toml;pyproject = fromTOML pyproject-toml;This will now use
builtins.fromTOML, I believe, making it ever so slightly less reproducible in the far future.i don't think
lib.fromTOMLactually exists?Oh! Then indeed, we can clean this up.
@ -54,0 +43,4 @@{from = schema;to = "./panel/configuration/schema.json";}Am I missing something or is this PR really just about these four lines, the rest just moving around but not changing code?
correct!
Looks good to me, then!
kiara referenced this pull request2025-06-04 20:52:28 +02:00