-
-
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 5 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
71 changes: 71 additions & 0 deletions
71
src/JsonApiDotNetCore/Graph/CamelCaseResourceNameFormatter.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,71 @@ | ||
using System; | ||
using System.Reflection; | ||
using Humanizer; | ||
using JsonApiDotNetCore.Models; | ||
using str = JsonApiDotNetCore.Extensions.StringExtensions; | ||
|
||
namespace JsonApiDotNetCore.Graph | ||
{ | ||
public class CamelCaseResourceNameFormatter : IResourceNameFormatter | ||
{ | ||
/// <summary> | ||
/// Uses the internal type name to determine the external resource name. | ||
/// By default we us Humanizer for pluralization and then we dasherize the name. | ||
/// </summary> | ||
/// <example> | ||
/// <code> | ||
/// _default.FormatResourceName(typeof(TodoItem)).Dump(); | ||
/// // > "todo-items" | ||
/// </code> | ||
/// </example> | ||
public string FormatResourceName(Type type) | ||
{ | ||
try | ||
{ | ||
// check the class definition first | ||
// [Resource("models"] public class Model : Identifiable { /* ... */ } | ||
if (type.GetCustomAttribute(typeof(ResourceAttribute)) is ResourceAttribute attribute) | ||
return attribute.ResourceName; | ||
|
||
return ApplyCasingConvention(type.Name.Pluralize()); | ||
} | ||
catch (InvalidOperationException e) | ||
{ | ||
throw new InvalidOperationException($"Cannot define multiple {nameof(ResourceAttribute)}s on type '{type}'.", e); | ||
} | ||
} | ||
|
||
/// <summary> | ||
/// Aoplies the desired casing convention to the internal string. | ||
/// This is generally applied to the type name after pluralization. | ||
/// </summary> | ||
/// | ||
/// <example> | ||
/// <code> | ||
/// _default.ApplyCasingConvention("TodoItems"); | ||
/// // > "todo-items" | ||
/// | ||
/// _default.ApplyCasingConvention("TodoItem"); | ||
/// // > "todo-item" | ||
/// </code> | ||
/// </example> | ||
public string ApplyCasingConvention(string properName) => str.Camelize(properName); | ||
|
||
/// <summary> | ||
/// Uses the internal PropertyInfo to determine the external resource name. | ||
/// By default the name will be formatted to kebab-case. | ||
/// </summary> | ||
/// <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(); | ||
/// // > "compound-property" | ||
/// </code> | ||
/// </example> | ||
public string FormatPropertyName(PropertyInfo property) => str.Camelize(property.Name); | ||
} | ||
} |
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
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.