Marcelo Glasberg
Marcelo Glasberg
I think your argument about being accessible and debuggable makes perfect sense, and I'm happy with it. But it's not always that we have control over the types we use....
@dnys1 maybe please still leave it open? We went on a tangent, but the issue was just about a minor improvement in the error message, by applying the What/Why/How format.
That's great! I renamed this issue to `Explain in the docs that Celest can serialize an exception imported from another package`. Just make it clear in the documentation.
It doesn't need to be a plugin, it could be just a CLI command. But IDE Plugins are sometimes just a more usable way to access the CLI. Being able...
* Show backend logs (including function prints) * Show some very visible icon depending if Celest is running locally or in the cloud.
* In the IDE Editor, when I CTRL-click in the `admin` or `doSomething` from `await celest.functions.admin.doSomething()` it should navigate to the function **definition**, not to the generated function implementation.
* Since it's not possible to make `celest` only visible in the frontend, and `celestBackend` only visible in the backend, the plugin must take care of that by marking their...
@caseycrogers > Your example with translation layers doesn't work for scenarios where a brand new field is added I think it works. It must, because my proposal basically lets you...
Yes, you are right. In `client.dart`: ```dart final celest = Celest(); final celestBackend = CelestBackend(); ``` Only problem is, since it's not possible to make `celest` only visible in the...