-
-
Notifications
You must be signed in to change notification settings - Fork 158
Allow for multiple naming conventions (camelCase vs kebab-case) #581
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
Merged
Merged
Changes from 12 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6f88360
feat: draft of DI-registered ApplicationModelConvention
maurei abcc5c0
feat: injectable IResourceNameFormatter and IJsonApiRoutingCOnvention…
maurei 6a2074b
test: kebab vs camelcase configuration
maurei 0080a98
feat: kebab vs camel completed
maurei de42844
chore: spacing
maurei 521d435
style: spacing
maurei 5cd83c4
refactor: share logic between resource name formatter implementations
maurei 3e3e259
docs: resource formatter comments
maurei db68304
docs: comments improved
maurei e62604d
chore: remove static reference to ResourceNameFormatter
maurei 70e1a9e
chore: reviewer fixes
maurei e7a731b
style: removed spacing
maurei c1e70af
style: removed spacing
maurei File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
40 changes: 40 additions & 0 deletions
40
src/JsonApiDotNetCore/Graph/ResourceNameFormatters/CamelCaseFormatter.cs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
using str = JsonApiDotNetCore.Extensions.StringExtensions; | ||
|
||
namespace JsonApiDotNetCore.Graph | ||
{ | ||
/// <summary> | ||
/// Uses kebab-case as formatting options in the route and request/response body. | ||
/// </summary> | ||
/// <example> | ||
/// <code> | ||
/// _default.FormatResourceName(typeof(TodoItem)).Dump(); | ||
/// // > "todoItems" | ||
/// </code> | ||
/// </example> | ||
/// <example> | ||
/// Given the following property: | ||
/// <code> | ||
/// public string CompoundProperty { get; set; } | ||
/// </code> | ||
/// The public attribute will be formatted like so: | ||
/// <code> | ||
/// _default.FormatPropertyName(compoundProperty).Dump(); | ||
/// // > "compoundProperty" | ||
/// </code> | ||
/// </example> | ||
/// <example> | ||
/// <code> | ||
/// _default.ApplyCasingConvention("TodoItems"); | ||
/// // > "todoItems" | ||
/// | ||
/// _default.ApplyCasingConvention("TodoItem"); | ||
/// // > "todoItem" | ||
/// </code> | ||
/// </example> | ||
public class CamelCaseFormatter: BaseResourceNameFormatter | ||
{ | ||
/// <inheritdoc/> | ||
public override string ApplyCasingConvention(string properName) => str.Camelize(properName); | ||
maurei marked this conversation as resolved.
Show resolved
Hide resolved
|
||
} | ||
} | ||
|
27 changes: 27 additions & 0 deletions
27
src/JsonApiDotNetCore/Graph/ResourceNameFormatters/IResourceNameFormatter.cs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
using System; | ||
using System.Reflection; | ||
|
||
namespace JsonApiDotNetCore.Graph | ||
{ | ||
/// <summary> | ||
/// Provides an interface for formatting resource names by convention | ||
/// </summary> | ||
public interface IResourceNameFormatter | ||
{ | ||
/// <summary> | ||
/// Get the publicly visible resource name from the internal type name | ||
/// </summary> | ||
string FormatResourceName(Type resourceType); | ||
|
||
/// <summary> | ||
/// Get the publicly visible name for the given property | ||
/// </summary> | ||
string FormatPropertyName(PropertyInfo property); | ||
|
||
/// <summary> | ||
/// Aoplies the desired casing convention to the internal string. | ||
/// This is generally applied to the type name after pluralization. | ||
/// </summary> | ||
string ApplyCasingConvention(string properName); | ||
} | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.