Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App structure: hApps #517

Merged
merged 36 commits into from
Feb 11, 2025
Merged

App structure: hApps #517

merged 36 commits into from
Feb 11, 2025

Conversation

pdaoust
Copy link
Collaborator

@pdaoust pdaoust commented Jan 22, 2025

Closes #489. Depends on #516 , which depends on #512. Don't review until those are merged, cuz otherwise this PR will seem bigger than it really is.

@pdaoust pdaoust force-pushed the feat/guide/app-structure-happs branch from 8aabff7 to dbb573b Compare January 23, 2025 17:20
@pdaoust pdaoust requested review from zippy and mattyg January 23, 2025 17:21
@pdaoust pdaoust marked this pull request as ready for review January 23, 2025 17:21
@pdaoust pdaoust requested a review from c12i February 5, 2025 18:44
zippy
zippy previously approved these changes Feb 10, 2025
Copy link
Member

@zippy zippy left a comment

Choose a reason for hiding this comment

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

Minor fixes suggestions. Looks good as a first pass. I think we need to improve how we talk about scaffold based instructions or the "do-it-yourself" instructions. I think it might make sense that in our first level build we assume that code was generated from the scaffold, and then describe how to tweak the files generated from it. Then the hc app init and hc web-app init commands are in a separate "so-you-wanna-do-this-the-hard-way" section.

Co-authored-by: Eric Harris-Braun <eric@harris-braun.com>
@pdaoust pdaoust enabled auto-merge (squash) February 10, 2025 23:10
@pdaoust
Copy link
Collaborator Author

pdaoust commented Feb 10, 2025

Minor fixes suggestions. Looks good as a first pass. I think we need to improve how we talk about scaffold based instructions or the "do-it-yourself" instructions. I think it might make sense that in our first level build we assume that code was generated from the scaffold, and then describe how to tweak the files generated from it. Then the hc app init and hc web-app init commands are in a separate "so-you-wanna-do-this-the-hard-way" section.

Agreed, and I'm moving more and more to the "just show it the way it would be if it were scaffolded" approach -- I've removed or deprioritised a lot of the DIY stuff already in this and future PRs, and I can see it being a good thing to hide it in an expandable section or an addendum or something.

Copy link
Member

@zippy zippy left a comment

Choose a reason for hiding this comment

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

Looks good

@pdaoust pdaoust merged commit d3f0ab5 into main Feb 11, 2025
6 checks passed
@pdaoust pdaoust deleted the feat/guide/app-structure-happs branch February 11, 2025 00:40
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.

App structure 3: hApp and webHapp manifest and bundle formats
3 participants