You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2021/02/12 09:14:00 UTC

[jira] [Updated] (IGNITE-14169) .NET support standart java, .net naming conventions

     [ https://issues.apache.org/jira/browse/IGNITE-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikolay Izhikov updated IGNITE-14169:
-------------------------------------
    Fix Version/s:     (was: 2.11)
                   2.10

> .NET support standart java, .net naming conventions
> ---------------------------------------------------
>
>                 Key: IGNITE-14169
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14169
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.9.1
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: .net
>             Fix For: 2.10
>
>
> 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)