Skip to content

Conversation

@kostaspro
Copy link

Description

Fix proxy generation problems for the enum types in method signature

Checklist

  • I fully tested it as developer / designer and created unit / integration tests
  • I documented it (or no need to document or I will create a separate documentation issue)

How to test it?

public enum AddressType { One = 1, Two = 2 } public class SearchAppService : IApplicationService { public async Task GetAddressHintAsync(string searchString, AddressType? addressType) { } }

Expected result

getAddressHint = (searchString: string, addressType: AddressType, config?: Partial) => this.restService.request({ method: 'GET', url: '/api/search/address-hint', params: { searchString, addressType }, }, { apiName: this.apiName,...config });

Current result

getAddressHint = (searchString: string, addressType: enum, config?: Partial) => this.restService.request({ method: 'GET', url: '/api/search/address-hint', params: { searchString, addressType }, }, { apiName: this.apiName,...config });

@CLAassistant
Copy link

CLAassistant commented Mar 4, 2025

CLA assistant check
All committers have signed the CLA.

@kostaspro kostaspro changed the title Angular - Fix proxy generation problems for the enum types in method signature Angular - Fix proxy generation problems for the nullable enum types in method signature Mar 4, 2025
@stale
Copy link

stale bot commented Jul 18, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Jul 18, 2025
@stale stale bot closed this Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants