-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
"liquidart create newapp" Unhandled exception: Bad state: No element #5
Comments
This is part of the error caused by the migration to Null Safety of the package. I have been trying to fix this for a day, so far, there is no good news. Leave this issue open. I will post updates related to the issue here. |
I just found out that this issue pertains to the Dart language, and has been reported in the Dart project previously.
The orElse part of the code is what's causing the error. We have to replace that part with a conditional statement. There are more than 150 parts in the Liquidart project where this pattern of code occurs. I have already started fixing it. |
Please read Issue 7: Liquidart will be rewritten from scratch to understand the status of this issue and the Liquidart project. |
Tanks :) |
I had forked Aqueduct for customization, after learning about Liquidart I changed some Aqueduct packages to those of Liquidart. |
@EddieKamau do you mind making a PR to this repo's |
I will be checking in a few
…On Wed, May 19, 2021 at 1:36 PM Aldrin Mathew ***@***.***> wrote:
@EddieKamau <https://github.com/EddieKamau> do you mind making a PR to
this repo's main branch from your fork once it is completed? Also, I have
sent an email regarding this. Kindly check when you have time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJKQX633AMKA7EUCMLOJTT3TOOIC3ANCNFSM43IGXKQA>
.
--
*CrazyGenius*
|
Dart SDK version: 2.12.3 (stable) (Wed Apr 14 11:02:39 2021 +0200) on "windows_x64"
The text was updated successfully, but these errors were encountered: