Factory: spec chat writes setup.json, filed as .factory/setup.json
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
1897dd1e0a
commit
962d37e485
7 files changed
+49
-6
No files matched your search
+29
-4
@@ -1188,7 +1188,10 @@ How to work:
|
||||
2. Keep the spec in the file `spec.md` in your working directory and update it as the conversation moves on. Structure: Goal · Users · Features (numbered, each with acceptance criteria that can be checked by looking at the running app) · Non-functional requirements · Tech stack · Out of scope · Open questions.
|
||||
3. Be concrete: exact texts, limits, behaviour on errors. Point out contradictions and gaps instead of guessing.
|
||||
4. Do not build the software and do not touch other files. Do not create repositories yourself.
|
||||
5. When the user says the spec is done, propose a short project name and a repository slug (lowercase, digits and dashes) and end your message with exactly one fenced json block and nothing after it:
|
||||
5. Also keep the file `setup.json` in your working directory: it tells the acceptance stage how to start the finished app, so the app can be checked by looking at it. Once the tech stack is settled write it, and update it when the stack changes. Format (one JSON object, all values strings, no comments):
|
||||
`{"install": "optional one-off setup command, e.g. npm ci", "start": "command that runs the app in the foreground", "url": "where it listens, e.g. http://localhost:8080"}`
|
||||
Ask the user for the port and commands if the spec leaves them open. A static site may use e.g. `"start": "python3 -m http.server 8080"`. Without a start command acceptance has to guess, so do not skip this file for anything that runs.
|
||||
6. When the user says the spec is done, propose a short project name and a repository slug (lowercase, digits and dashes) and end your message with exactly one fenced json block and nothing after it:
|
||||
```json
|
||||
{"decision": "ready", "name": "Project name", "slug": "project-name", "description": "one sentence"}
|
||||
```
|
||||
@@ -1269,9 +1272,14 @@ pub fn slugify(s: &str) -> String {
|
||||
out.trim_end_matches('-').chars().take(60).collect::<String>().trim_end_matches('-').to_string()
|
||||
}
|
||||
|
||||
/// Is this a usable `.factory/setup.json`: a JSON object with a non-empty `start` command?
|
||||
pub fn valid_setup(text: &str) -> bool {
|
||||
serde_json::from_str::<Value>(text).ok().is_some_and(|v| v["start"].as_str().is_some_and(|s| !s.trim().is_empty()))
|
||||
}
|
||||
|
||||
/// Create the repository, file README and spec, register the repository and open the issue
|
||||
/// that starts the workflow. Safe to repeat after a failure: an empty repository is reused.
|
||||
pub async fn create_project(app: &Arc<App>, user: &User, settings: &mut FactorySettings, spec: &str, connection: &str, name: &str, slug: &str, description: &str, owner: &str) -> Result<Value> {
|
||||
pub async fn create_project(app: &Arc<App>, user: &User, settings: &mut FactorySettings, spec: &str, setup: &str, connection: &str, name: &str, slug: &str, description: &str, owner: &str) -> Result<Value> {
|
||||
let slug = slugify(slug);
|
||||
if slug.len() < 2 {
|
||||
bail!("the repository name is too short");
|
||||
@@ -1308,7 +1316,14 @@ pub async fn create_project(app: &Arc<App>, user: &User, settings: &mut FactoryS
|
||||
let id: crate::gitcreds::GitSettings = app.store.user_setting(&user.id, "git").unwrap_or_default();
|
||||
let (who, mail) = (Some(id.name.trim()).filter(|n| !n.is_empty()).unwrap_or("CodeCraft Factory").to_string(), Some(id.email.trim()).filter(|n| !n.is_empty()).unwrap_or("factory@codecraft.local").to_string());
|
||||
git(&resolved, &dir, &["checkout", "-B", "main"]).await?;
|
||||
git(&resolved, &dir, &["add", "README.md", "docs"]).await?;
|
||||
let mut add = vec!["add", "README.md", "docs"];
|
||||
let setup_filed = valid_setup(setup);
|
||||
if setup_filed {
|
||||
std::fs::create_dir_all(dir.join(".factory"))?;
|
||||
std::fs::write(dir.join(".factory/setup.json"), setup)?;
|
||||
add.push(".factory");
|
||||
}
|
||||
git(&resolved, &dir, &add).await?;
|
||||
git(&resolved, &dir, &["-c", &format!("user.name={who}"), "-c", &format!("user.email={mail}"), "commit", "-m", &format!("Add specification for {name}")]).await?;
|
||||
git(&resolved, &dir, &["push", "-u", "origin", "main"]).await?;
|
||||
|
||||
@@ -1318,7 +1333,7 @@ pub async fn create_project(app: &Arc<App>, user: &User, settings: &mut FactoryS
|
||||
let issue = g.create_issue(name, &format!("{}\n\nSpec: {spec_path}", description.trim()), &[cfg.label.clone()]).await?;
|
||||
let n = issue_no(&issue);
|
||||
app.store.factory_issue_add(&cfg.url, n, &user.id, name, &login)?;
|
||||
Ok(json!({"url": cfg.url, "repo": created["full_name"], "issue": n, "issue_url": issue["html_url"], "spec": spec_path}))
|
||||
Ok(json!({"url": cfg.url, "repo": created["full_name"], "issue": n, "issue_url": issue["html_url"], "spec": spec_path, "setup": setup_filed}))
|
||||
}
|
||||
|
||||
#[cfg(test)]
|
||||
@@ -1447,6 +1462,16 @@ mod tests {
|
||||
assert!(SPEC_INSTRUCTIONS.contains("\"decision\": \"ready\""));
|
||||
}
|
||||
|
||||
#[test]
|
||||
fn setup_json_needs_a_start_command() {
|
||||
assert!(valid_setup(r#"{"start": "npm start", "url": "http://localhost:3000"}"#));
|
||||
assert!(!valid_setup(r#"{"start": " "}"#));
|
||||
assert!(!valid_setup(r#"{"url": "x"}"#));
|
||||
assert!(!valid_setup("not json"));
|
||||
assert!(!valid_setup(""));
|
||||
assert!(SPEC_INSTRUCTIONS.contains("setup.json"));
|
||||
}
|
||||
|
||||
#[test]
|
||||
fn encodes_labels() {
|
||||
assert_eq!(urlenc("factory:qa"), "factory%3Aqa");
|
||||
|
||||
Reference in new issue
Block a user