Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POST returns 500 when primarykey != entitynameID #30

Closed
pdevito3 opened this issue May 8, 2021 · 0 comments
Closed

POST returns 500 when primarykey != entitynameID #30

pdevito3 opened this issue May 8, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@pdevito3
Copy link
Owner

pdevito3 commented May 8, 2021

I'd expect to be able to submit a POST and get 201, but am getting 500

Steps to reproduce

A build like the below will have a broken POSt because PK is expecting ReportRequestId instad of ReportRequest. Need to fix to use primary key

DomainName: BrokenPost
BoundedContexts:
- SolutionName: Reporting
  Port: 1210
  DbContext:
   ContextName: ReportingDbContext
   DatabaseName: ReportingDbContext
   Provider: SqlServer
  Entities:
  - Name: ReportRequest
    Properties:
    - Name: ReportId
      IsPrimaryKey: true
      Type: guid
      CanFilter: true
      CanSort: true
    - Name: Provider
      Type: string
      CanFilter: true
      CanSort: true
    - Name: Target
      Type: string
      CanFilter: true
      CanSort: true
  SwaggerConfig:
    Title: RideRequest Swgger Doc
    Description: This is my swagger doc
    SwaggerEndpointName: "v1"
    AddSwaggerComments: true

Further technical details

Craftsman version (dotnet tool list -g): 0.9.3

@pdevito3 pdevito3 added the bug Something isn't working label May 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant