Skip to content

J/template hyperapp#380

Merged
jurij-jukic merged 27 commits intodevelopfrom
j/template-hyperapp
Oct 22, 2025
Merged

J/template hyperapp#380
jurij-jukic merged 27 commits intodevelopfrom
j/template-hyperapp

Conversation

@jurij-jukic
Copy link
Copy Markdown
Contributor

@jurij-jukic jurij-jukic commented Oct 10, 2025

Insert hyperapp skeleton into kit templates.

I made a few changes to hyperapp skeleton which are not easily visible here (due to the whole repo being new, rather than just diffs), so here are the relevant ones to inspect:

There is a few more but these are the significant ones. It's basically the changes required to make hyperapp-skeleton run out of the box with kit bs --hyperapp as soon it's generated from the template.

kit new --template hyperapp-skeleton skel-template-new-dir --ui works now.

@jurij-jukic jurij-jukic changed the base branch from master to develop October 10, 2025 12:38
[workspace]
members = [
"skeleton-app",
"target/hyperapp-skeleton-caller-utils",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove this; we want the wildcard below but not this one

the reason is for building from scratch: when building from scratch the wildcard version is happy but the non-wildcard version complains

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fresh builds work with or without that line for me. Remove the line or keep? Your choice.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove, just keep the wildcard

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Comment thread src/new/templates/rust/ui/hyperapp-skeleton/api/skeleton-app-dot-os-v0.wit Outdated

[features]
caller-utils = ["hyperapp_skeleton_caller_utils"]
default = ["caller-utils"]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should remove this because it will interfere with fresh builds. We should test to confirm/falsify: does this mess up building fresh?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, doesn’t make a diff with fresh builds. Remove or keep, your choice.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Comment thread src/new/templates/rust/ui/hyperapp-skeleton/skeleton-app/src/lib.rs Outdated
Comment thread src/new/templates/rust/ui/hyperapp-skeleton/skeleton-app/src/lib.rs Outdated
Comment thread src/new/templates/rust/ui/hyperapp-skeleton/skeleton-app/src/lib.rs Outdated
use hyperprocess_macro::hyperprocess;

// HYPERWARE PROCESS LIB IMPORTS
// These are provided by the hyperprocess_macro, DO NOT add hyperware_process_lib to Cargo.toml
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove these two comments

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment thread src/new/templates/rust/ui/hyperapp-skeleton/skeleton-app/src/lib.rs Outdated
Comment thread src/new/templates/rust/ui/hyperapp-skeleton/skeleton-app/src/lib.rs Outdated
@jurij-jukic
Copy link
Copy Markdown
Contributor Author

jurij-jukic commented Oct 15, 2025

any reason not to make file-explorer, id and sign subtrees in kit?
Update: its easier to copy paste when an update happens than the overhead of having a subtree. Not gonna build this.

@jurij-jukic
Copy link
Copy Markdown
Contributor Author

In the last commit, removed api.ts, and wired up caller-utils.ts correctly.

@jurij-jukic
Copy link
Copy Markdown
Contributor Author

Re previous change request to remove vite-env.d.ts. Keeping that because it's useful in Vite projects.

@jurij-jukic
Copy link
Copy Markdown
Contributor Author

New file explorer wired up. Last detail - keeping the api folder in that one (since its an example, and we dont expect people to build it), or removing it?

Copy link
Copy Markdown
Member

@nick1udwig nick1udwig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost there, a few more comments

// UI state
isLoading: boolean;
error: string | null;
} No newline at end of file
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this file should be removed

Copy link
Copy Markdown
Contributor Author

@jurij-jukic jurij-jukic Oct 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the api related types (as thats LLM bad habit), but kept the interface SkeletonStore type as types/skeleton.ts is a clean place for LLMs to update types to match the rust backend

Comment thread src/new/templates/rust/ui/hyperapp-skeleton/resources/guides/CHANGES_MADE.md Outdated
@@ -0,0 +1,2 @@
// Re-export everything from caller-utils
export * from '../../../target/ui/caller-utils'; No newline at end of file
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Future TODO: remove these ui/src/types/api.ts files and update imports to point to the caller-utils file themselves. This api.ts is a bad pattern that LLMs are already prone to, so we shouldn't demo it for them even more

@@ -0,0 +1,2 @@
// Re-export everything from the generated caller-utils
export * from '../types/api'; No newline at end of file
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto on "future TODO": eventually remove this

Comment thread src/new/templates/rust/ui/hyperapp-skeleton/README.md Outdated
Comment thread src/new/templates/rust/ui/hyperapp-skeleton/README.md Outdated

### 5. Rename as appropriate

Change names throughout from `skeleton-app` (and variants) as appropriate if user describes app name.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the name should match the template name (i.e. both should be hyperapp-skeleton) throughout so that kit will appropriately rename stuff throughout (i.e. when you do kit new foo --template hyperapp-skeleton --ui it will rename the package and process to foo -- but only if the names throughout properly match the template name)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so I renamed it here to hyperapp-skeleton, but imo this deserves its own PR to make sure kit renames things properly (and should be done by kit rather than llms to be deterministic). Just at first glance, e.g. metadata.json doesn't get changed at all, and there are likely other places which require renaming. So, punt for other PR?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, we can push back to another PR, but if so we are agreeing we will not make a new kit release until we have it in

Comment thread src/new/templates/rust/ui/hyperapp-skeleton/README.md
@nick1udwig
Copy link
Copy Markdown
Member

New file explorer wired up. Last detail - keeping the api folder in that one (since its an example, and we dont expect people to build it), or removing it?

I'm fine keeping it, but we should add a note in README or something to that effect

Copy link
Copy Markdown
Member

@nick1udwig nick1udwig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, nice work! let's merge and make some follow-up issues so we don't lose track of the TODOs here in the comments

@jurij-jukic jurij-jukic merged commit ca8f4cc into develop Oct 22, 2025
1 check passed
@jurij-jukic jurij-jukic deleted the j/template-hyperapp branch October 22, 2025 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants