David Brochart

The following components are now available on conda-forge: - https://github.com/conda-forge/asphalt-feedstock - https://github.com/conda-forge/asphalt-web-feedstock - https://github.com/conda-forge/asphalt-sqlalchemy-feedstock - https://github.com/conda-forge/asphalt-serialization-feedstock - https://github.com/conda-forge/asphalt-redis-feedstock - https://github.com/conda-forge/asphalt-mailer-feedstock - https://github.com/conda-forge/asphalt-exceptions-feedstock - https://github.com/conda-forge/asphalt-templating-feedstock - https://github.com/conda-forge/asphalt-py4j-feedstock - https://github.com/conda-forge/asphalt-mongodb-feedstock

In [pycrdt](https://github.com/jupyter-server/pycrdt) I'm experimenting with [pydantic](https://docs.pydantic.dev) models to validate incoming changes, by first applying the changes to a "twin" document of the "real" document, and if the "twin" document is...

> In principle this could be solved by extending the ModelDB, right? We could have `changedDeep` signal as well. Maybe but it's not the only missing feature.

> we have today a ydoc package that proves that the abstraction approach makes sense It only proves that we made it work with the modelDB abstraction, but as I...

Of course not, but `YNotebook` would not use modelDB anymore.

Sorry if I'm not clear enough. I just want to drop the modelDB abstraction, both in JupyterLab and jupyter-ydoc. No abstraction layer anymore, I hope that this is clear.

When I say using Yjs directly, I don't mean getting rid of jupyter-ydoc's API, but not using the `observables` package as an abstraction layer on top of Yjs in JupyterLab.

> Is it the `observables` or the Lumino signals you want to get ride off? Only the `observables` package. Yjs doesn't have the equivalent of signals. But the changes emitted...

bot please update galata snapshots

> bot please update galata snapshots It looks like I cannot talk to the bot :smile: