-
Notifications
You must be signed in to change notification settings - Fork 48
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
CLI (MariaDB/MySQL>tbls>liam) only generates a schema.json in dist/ #751
Comments
Same results. The generated schema.json looks correct but no HTML/CSS/Javascript is generated.
|
Thank you for your feedback! Have you tested this on Windows? @ATroschke @toddsmith-adsk The reason I ask is that this part of the CLI is still in its initial implementation, and I suspect that some naive assumptions in the code might be affecting the outcome. |
Yes on windows |
Indeed, on Windows. I will be checking this in WSL again tomorrow. |
@mtsmith @ATroschke Thank you both for your responses! The code at liam/frontend/packages/cli/src/cli/erdCommand/buildCommand/index.ts Lines 51 to 53 in 2a6006c
might not work on Windows. It could behave differently in WSL. I plan to recheck this by tonight, Tokyo time. |
FYI If I run in a bash terminal it will work on Windows. A WSL, Powershell or Command Prompt terminal will fail. |
The issue should be resolved in I just verified it using PowerShell on my Windows PC. |
It now properly generates the other files as well, thanks for the fix on windows! |
Self Checks
Cloud or Self Hosted
Self Hosted
Version (only for Self Hosted)
0.4.1
Steps to reproduce
npx @liam-hq/cli erd build --format tbls --input docs/schema.json
Expected Behavior
A proper static page in dist/
Actual Behavior
Only a single schema.json in dist/ - without any webpage code to host. I should note both the tbls docs and schema.json are indeed valid.
Additional Context
For the sake of company guidelines, I am unable to share any schema specifics. At most I could reproduce the issue with a quick docker-compose setup, but as this fails after the tbls step (as said the tbls documentation is valid) - this should be easily reproducible.
The text was updated successfully, but these errors were encountered: