Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

echo is now dropped al level 3, could/should be 2? #26

Closed
Felienne opened this issue Mar 18, 2020 · 1 comment
Closed

echo is now dropped al level 3, could/should be 2? #26

Felienne opened this issue Mar 18, 2020 · 1 comment

Comments

@Felienne
Copy link
Member

But this could be level 2 too? It is not really needed anymore once we have variables.
@Felienne Felienne changed the title ask is now dropped al level 3 echo is now dropped al level 3, could/should be 2? Mar 18, 2020
@arjenpdevries
Copy link
Contributor

Good question.

My kids were confused that a line starting with ask did not work any more. Maybe consistency should be increased, or the lecture put more emphasis on this change.

fpereiro pushed a commit that referenced this issue May 18, 2021
Implemented an addition catch to provide more useful feedback from th…
9ab37c1 
…e GFM model in the case of a client error. Ideally these never occur, but it might still be the case. This solves and fixes #26.
@hedyorg hedyorg locked and limited conversation to collaborators Oct 10, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arjenpdevries @Felienne