Question: Will SignalR still be part of the core in v14 or does my package need to set it up?

I know we are looking to use it in the future for real time updates and such, but don't know the current status of the setup right now. Lemme grab the laptop and have a quick poke 😉

you need the npm package, but i think the c# libraries are still in the core. https://github.com/KevinJump/uSync/tree/v14/dev/uSync.Backoffice.Management.Client/assets/src/signalr

The mighty Kevin to the resque once again #h5yr!

Thanks Kevin nice way to wrap the js hub as a context

yeah - it turned out much neater than i hoped, (i think i will prob make it more generic when it then is needed in uSync.Complete)

Registering a hub in c# still the same just namespace changes?

yes, i think so. we register a root via an umbraco pipeline.

🤔 old pipeline filters, time to do another round of cleanup 😁

Thanks both. Just had a quick skim through your branch Kevin seems your far along 💪

yeah - uSync is 'beta' ready 🙂

Haha thought as much !!

I don't think dropping an old usync folder in and importing will work for the beta though. but working on it.

Now you done the bulk. Is there anything you would share or type up as more notes in dev.to posts?

Quite a lot of datatype cleanups happened and a few more minor ones incomming. Keep an eye on the DB migrations (and possible dashboard auto cleanup stuff)

yes - i might do a bit more on train tommorow, I have an idea for a 'simple' server communication setup (e.g not element, context, repo, store, source, resource 🙂

Yeh I simplified mine for now. Just too much for my needs right now

yes - main hurdle to a beta uSync has been the moving datatypes 😉 - some minor conversions can get a -> b , but we have usync.Migrations to do grid -> block grid, and my ideal. is a button, that detects old uSync folder and says "shall we convert this for you" ... but not for beta

Henry Jump?! Your twin bro who also loves to code?

Son... growing the business.

😄