Kevin Jump
04/11/2024, 11:02 AMWarren Buckley
04/11/2024, 12:14 PMWarren Buckley
04/11/2024, 3:39 PMWarren Buckley
04/11/2024, 8:51 PMWarren Buckley
04/13/2024, 6:49 PMWarren Buckley
04/14/2024, 5:18 PMnobody7781
04/16/2024, 1:41 PMRichard Soeteman
04/16/2024, 2:42 PMJacob Overgaard
04/17/2024, 9:50 AMKevin Jump
04/17/2024, 10:10 AMJacob Overgaard
04/17/2024, 10:40 AMKevin Jump
04/17/2024, 10:53 AMRichard Soeteman
04/17/2024, 11:31 AMRichard Soeteman
04/17/2024, 11:31 AMKevin Jump
04/17/2024, 11:54 AMJacob Overgaard
04/17/2024, 12:01 PMWarren Buckley
04/17/2024, 2:28 PMKevin Jump
04/19/2024, 12:32 PMOperationIdSelector
with something that checks for your api end point and then only applies that.
- replace umbracos in a build builder.Services.AddSingleton<IOperationIdSelector, MyOperationIdSelector>();
my convern here is that this isn't sustainable ?
if i register .AddSingleton<IOperationSelector, uSyncOperationSelector>
and then someone else comes along and reigsters .AddSingleton<IOperationSelector, SuperCustomIdSelector>
doesn't that mean that my customId selector will never then be used ?
---
I think (and i might be wrong) that what i should actually do, is only register my custom selector on the site i am using to generate my API from and not actually put it in the solution ? because as far as i can tell once the typescript files have been generated they are using the path not the id, so it doesn't matter ?Kevin Jump
04/19/2024, 2:44 PMuSync.Publisher
uses code from uSync.Expansions.Core
and uSync
when this is custom elements (like <usync-report-view>
or something) then this all works fine, because really there is no code .
but now because i am being tidy, i've just moves some of the code from the publisher package into the "core" one, and i want to base the publisher stuff of these core elements.
e.g
in my usync-expansions
module i have a base SignalRHub class. SyncSignalRHub
and inside my uSync.Publisher code i want to base off that.
ts
import { ISyncUpdateMessage, SyncSignalRHub } from '@jumoo/usync-expansions/processing';
export class SyncPublisherSignalRHub extends SyncSignalRHub {
i've build and publish (to a private npm repo) the usync-expansions module, included it and
this all works lovey .... in vscode.
but when i got to umbraco, with this i get the following ...
Uncaught (in promise) TypeError: Failed to resolve module specifier "@jumoo/usync-expansions/processing". Relative references must start with either "/", "./", or "../".
which i think it because the build process publisher model has compile the code down, but left in the refrences to the model
i can see this in the compiled javascipt
import { SyncSignalRHub as Rn, SyncProcessingBaseContext as In, SyncProcessingElement as xn } from "@jumoo/usync-expansions/processing";
a) now i think what i actually want it to do is compile the code into the "publish" module ? so it doesn't attempt to load something that isn't there ?
or
b) is there something i should be doing so @jumoo/usync-expansions
works in the browser
i suspect its a)
anyone know the secret source to get (a) working ?Warren Buckley
04/22/2024, 8:12 PMRichard Soeteman
04/23/2024, 8:32 AMKevin Jump
04/23/2024, 12:08 PMRichard Soeteman
04/24/2024, 6:37 AMDean Leigh
04/24/2024, 9:47 AMD_Inventor
04/24/2024, 3:49 PMEntity Action
working that opens a panel, much like the old menu items with the LaunchDialogView
options. In particular for content items in the content tree. I'm struggling to get this to work, does anybody happen to have something already that I can Extension of alias "contentgenerator.entity.action" did not succeed creating an Element with Api, Api was created but the Element was missing a JavaScript file via the 'element' or the 'js' property. Alternatively define a Element Name in 'elementName' in the manifest.
I'll give some more context in a threadPaul Daly (uSkinned.net)
04/25/2024, 10:03 AMPaul Daly (uSkinned.net)
04/25/2024, 10:04 AMrickbutterfield
04/25/2024, 12:05 PMWarren Buckley
04/25/2024, 8:06 PM