Skip to content

Conversation

nagybalint001
Copy link

I have updated the nuget packages to the latest versions.

NJsonSchema had some interface changes, I'm not sure that I have replaced everything correctly.
I also updated the SignalR version in the Core project, the newer version is part of the aspnet core framework, which can't be referenced in a netstandard project, that's why I changed the targetframeworks. (I couldn't find a workaround to reference the newer version of SignalR without this change.)

The output of the new version is the same, except for this part (undefined):

export interface Person {
    firstName: string | undefined;
    lastName: string | undefined;
}

export interface Event {
    Type: string | undefined;
}

But according to the C# classes this seems OK to me.

@RicoSuter
Copy link
Owner

Thanks for the PR, first check looks very good.

operation.Parameters[arg.Name] = parameter;
}

var returnType =
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check: This must be a proper contextual type to carry NRT info

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed one bug here, is this what you were thinking of? 793d919

var hubModel = new HubModel(hub.Key, hub.Value, resolver);
var template = _settings.TypeScriptGeneratorSettings.TemplateFactory.CreateTemplate("TypeScript", "Hub", hubModel);
artifacts.Add(new CodeArtifact(hubModel.Name, CodeArtifactType.Class, CodeArtifactLanguage.TypeScript, template));
artifacts.Add(new CodeArtifact(hubModel.Name, CodeArtifactType.Class, CodeArtifactLanguage.TypeScript, CodeArtifactCategory.Undefined, template));
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a new category?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think Client should be good for this, I fixed this.

@RicoSuter
Copy link
Owner

Looks good. Ill check the open comments

@RicoSuter
Copy link
Owner

Any updates on this?

@RicoSuter
Copy link
Owner

Ref: #2 (comment)

Cant we use .NET Core 3.0 for more compatibility?

@RicoSuter
Copy link
Owner

@TomSmith27 are there things here we still need to merge?

@TomSmith27
Copy link
Contributor

Looks like this updates to .NET core 3 which could be useful to do however there are conflicts because of the updates i made

@RicoSuter
Copy link
Owner

Do you still want to merge this PR?
Can you fix the conflicts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants