OData / OData/AspNetCoreOData

Issue when using camelcase enums

Open
#638 1 comment 0 reactions 1 assignee View on GitHub

@corranrogue9 is already working on this.

Since Jul 19, 2022.

investigating
Dominant language
C#
Stars
505
Forks
186
PR merge metrics
No merged PRs in 30d

Description

Assemblies affected
Hypothetical version with latest ModelBuilder, and latest version

Describe the bug
When investigating if we needed changes to support the new camelcase enum feature from ModelBuilder, I discovered a couple of issues.

  1. When using the new feature, this test case fails when the correct casing is used for the enum. Is this how we want to support camel casing? That only camel casing is allowed?
  2. This test does not succeed either. It should find the single entity with the Third key. Note that neither casing (third or Third) works. I think that there is a bug when using an enum as a key. Once that bug is fixed, we should also investigate if the camel casing is supported when routing.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.