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
feat: cli improvement #55
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @DeleMike 👋
Great work! I love the speed of PR 🔥
I have a few comments on the PR. Do let me know if you require any more information from me. 😄
Also, answering your question here.
It is because it will either expect a relative path or an absolute path. So, it is unable to find the folder as you do not have any folder named You can decipher it from the error message here
So, it is not a fixed value but this is the expected error. |
Hi @sansyrox, I have updated the implementation - I made some changes with your suggestions, thanks! The issue now is this command I compared it against the So because
I tried printing the absolute path and it is pointing to the right directory Am I missing a step during compilation? |
I mistakenly deleted the whole project while testing if the compilation was working but I was able to get the files back later.
|
Okay, so an update. I saw that the The only question I have now is the build method only produced this file structure:
are there not meant to be more files? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @DeleMike 👋
Thank you for addressing the changes. However, I have a few more comments on this PR. Do let me know if you require any more clarification 😄
@DeleMike , there should be more files, given that we have merged the dev and the build flags. The |
@sansyrox Can you please check this: if build:
# Start/run project
build_dir = os.path.join(path, "build")
subprocess.run(
[sys.executable, "-m", "build"],
cwd=build_dir,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE,
)
else:
# Compile and build project
compile(os.path.join(path, "__init__.py"))
create_main_file(path) Does the above actually represent that we have merged the two flags? You suggested that I should not compile if |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @DeleMike 👋
Great work. I have left a few suggestions.
Also, I will be pushing a commit to fix the large diffs soon 😄
170be6c
to
f1eaaa1
Compare
Hello @sansyrox , Thanks for your suggestions. I have used them to make updates. |
Thanks @DeleMike 😄 I have made a few changes finally. And this should be good to merge. Great work! 🔥 |
Actually @DeleMike , one update. The build script has stopped working. If you delete the build and the dist folder. And then re start the |
Thanks. I'm looking into it now... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Great work @DeleMike ! 🔥 ❇️
Closes #47
I have done some research and added
--dev/--no-dev
and--build/--no-build
instead of the former commands. This new option style allows the build file to now haspython3 starfyre --build --path="test-application"
. It makes the command leaner.If the user runs the build file, it will successfully build and run the required files to create our application.
Things Observed:
If I change the build file from
python3 starfyre --build --path="test-application"
topython3 starfyre --build --path="my-first-app"
. It will report the following error:Is this an expected behaviour?
Is the
--path="test_application"
in the command contained in the starfyre build file constant orpath
value can change?