You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for quicker debugging, when Elide is scanning an non-existing data model package, Elide service is better with not starting successfully but through an Exception instead.
Current Behavior
When we configure Elide by binding a non-existing data model package, Elide started up successfully without any errors.
This leads to a confusing user who sees both a happy-running Elide but an empty database
Possible Solution
I think it might be a simple check during scanning phase if Elide team merits such proposed change
The text was updated successfully, but these errors were encountered:
Expected Behavior
In order for quicker debugging, when Elide is scanning an non-existing data model package, Elide service is better with not starting successfully but through an Exception instead.
Current Behavior
When we configure Elide by binding a non-existing data model package, Elide started up successfully without any errors.
This leads to a confusing user who sees both a happy-running Elide but an empty database
Possible Solution
I think it might be a simple check during scanning phase if Elide team merits such proposed change
The text was updated successfully, but these errors were encountered: