[
https://issues.apache.org/jira/browse/IGNITE-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14169:
------------------------------------
Fix Version/s: (was: 2.10)
2.11
> .NET support standart java, .net naming conventions
> ---------------------------------------------------
>
> Key: IGNITE-14169
> URL: https://issues.apache.org/jira/browse/IGNITE-14169
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 2.9.1
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently, {{BasicBinaryNameMapper[isSimpleName=false]}} assumes that type
> names equals both in Java and .Net.
> Java type - {{ru.company.Model}}
> .Net type - {{ru.company.Model}}
> However, .net naming conventions [1] differs from java [2]
> So, if a user follows both conventions then names will be
> Java type - {{ru.company.Model}}
> .Net type - {{Ru.Company.Model}}
> We should support standard naming conventions for both platforms in
> {{BasicBinaryNameMapper[isSimpleName=false]}}.
> [1]
> https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces
> [2]
> https://www.oracle.com/java/technologies/javase/codeconventions-namingconventions.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
