-
Notifications
You must be signed in to change notification settings - Fork 20
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
Show Output of the Commands #118
Comments
Isaac's Team |
Hi @griffinh1, please note that the completion of this issue will depend on the completion of many other issues. That is, we cannot show the output of the commands until the commands themselves are their interfaces are correctly defined. |
Hi @griffinh1 @barrezuetai, I am just wondering if this issue has been solved or not. If not, it is probably a good idea to pass to @paladp. He is working on Issue#139 and Issue#162 and both of these two issues are related to |
@Lancasterwu: Our team is finishing up the Django documentation right now and should be able to be submitted by tomorrow afternoon. |
@barrezuetai I thought this issue is not directly related to the Django feature. Shouldn't the output we put in |
They're related. In the Django documentation we talk about how to set up the environment and which commands are used to run/test django @Lancasterwu |
@barrezuetai @finneyj2 what is the status of the work on this issue? Please update it in the project board to either |
@Alex-Yarkosky I talked to @barrezuetai and it hasn't been worked on, hence why I picked it up. |
The README file currently shows how commands are run, but, first, this does give a prompt symbol,
$
, to indicate that they are commands for execution. Also, the README does not give any output of these commands. This should be added to the README, along with the discussion of the trade-offs inherent in the different teams.The text was updated successfully, but these errors were encountered: