feat(cli): enable frontend.vue template, bump to 26.9.0, fix frontend token replacement - #104
Merged
Merged
Conversation
…oken replacement for frontend files
- Enable template.frontend.vue: dynamiatools/template-frontend-vue now
has a functional scaffold (Vite + Vue 3 + @dynamia-tools/tailadmin-vue
+ @dynamia-tools/sdk + @dynamia-tools/vue), verified end-to-end
through the actual CLI (clone + token replace), and via a full
pnpm install + type-check + build against the currently-published
@dynamia-tools/sdk@26.8.0/@dynamia-tools/vue@26.8.0 (26.9.0 isn't
published yet -- see below).
- Bump dynamia.version / npm.sdk.version / npm.ui-core.version /
npm.vue.version from 26.4.1 to 26.9.0: this release's target version
per Mario. Not yet published to Maven Central/npm as of this commit --
generated backend projects (and this frontend template's package.json)
will fail to resolve dependencies until it ships. Once published, no
further template changes are needed.
- Fix replaceTokensInDir's TEXT_EXTENSIONS allow-list (replace.ts): it
was missing .ts/.tsx/.js/.jsx/.vue/.html/.css/.scss entirely, so
{{PROJECT_NAME}} would have silently survived generation in every
frontend template's actual source/markup files -- only package.json
(.json) was ever getting replaced. Found and fixed while building
template-frontend-vue. Added a regression test.
Also updates the backend templates' <dynamia.version> pom.xml property
and this file's matching replace.ts fallback string to 26.9.0 (separate
commits in each template repo).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UcARdenC1Sk5EVpkzboH9W
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #91 -- last piece: frontend.vue.
Enables
template.frontend.vuenow that dynamiatools/template-frontend-vuehas a real scaffold (commit a9a510a): Vite + Vue 3 + TS, using
@dynamia-tools/tailadmin-vuefor the admin shell insteadof a bare Vite starter, wired to
@dynamia-tools/sdk(DynamiaClient) and@dynamia-tools/vue(DynamiaVueplugin,
useNavigation).Also in this PR
dynamia.version,npm.sdk.version,npm.ui-core.version,npm.vue.version) --this release's target version per Mario. Not published yet to Maven Central/npm as of this PR -- generated
Java/Kotlin/Groovy backends and the new Vue frontend template will fail to resolve dependencies until it ships.
Nothing else needs to change once it's out.
replaceTokensInDir'sTEXT_EXTENSIONSallow-list was missing.ts/.vue/.html/.js(and a fewothers) entirely -- only
.jsonfiles were ever getting{{PROJECT_NAME}}replaced for frontend templates, soevery actual source/markup file would have silently shipped the literal token. Found while building
template-frontend-vue; added a regression test.Verification
pnpm run test-- 32/32 passing (includes the new regression test).dynamia new --scaffold frontend --frontend vue --yes --no-gitagainst the real repo -- clone + tokenreplacement both correct (
package.jsonname,index.htmltitle).pnpm install && pnpm run build(type-check + Vite build) on the template, and again on a simulatedpost-token-replacement copy -- both clean, run against the currently-published
@dynamia-tools/sdk@26.8.0/@dynamia-tools/vue@26.8.0(since 26.9.0 isn't out yet).pnpm installon the actual CLI-generated project fails as expected with a cleanERR_PNPM_NO_MATCHING_VERSIONfor@dynamia-tools/vue@^26.9.0-- confirms nothing else is broken, just waitingon the real publish.
frontend.reactremains disabled/placeholder -- leaving it there for now per Mario.🤖 Generated with Claude Code
https://claude.ai/code/session_01UcARdenC1Sk5EVpkzboH9W