Sets whether the model is collaborative or not when registering its factory

[hbcarlos]

Follow-up #13458

Hi @dlqqq, @ellisonbg and @fcollonval .

I like the idea of specifying whether the document is collaborative or not. Furthermore, I believe we should make it more robust by setting it as collaborative when registering the model factory.

References

Code changes

User-facing changes

Backwards-incompatible changes

[jupyterlab-probot]

Thanks for making a pull request to jupyterlab!
To try out this branch on binder, follow this link:

[fcollonval]

Thanks @hbcarlos

[fcollonval]

@meeseeksdev please backport to 3.6.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 3.6.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 4496969e65e66539c1327cc59fe684f206c858d4

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #13526: Sets whether the model is collaborative or not when registering its factory'

4. Push to a named branch:

git push YOURFORK 3.6.x:auto-backport-of-pr-13526-on-3.6.x

5. Create a PR against branch 3.6.x, I would have named this PR:

"Backport PR #13526 on branch 3.6.x (Sets whether the model is collaborative or not when registering its factory)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.