This is a migrated thread and some comments may be shown as answers.

Encapsulating fields with m_

1 Answer 30 Views
Refactorings
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Travis Johnson
Top achievements
Rank 1
Travis Johnson asked on 23 Jan 2014, 10:11 PM
currently, when i encapsulate a field such as
private string m_myFieldName

to a get/set property, 
this is what i get
public string MMyFieldName
{
get
{
                return m_myFieldName
;
        }
        set
        {
        m_myFieldName = value;
        }
}

Is there a way for me to tell the just code to ignore the m_prefix when encapsulating fields to Get/Set properties in order to just get
MyFieldName as the property name? 





1 Answer, 1 is accepted

Sort by
0
Zdravko
Telerik team
answered on 24 Jan 2014, 01:15 PM
Hi Travis,

I am afraid that JustCode can't ignore the prefix at the moment. It is part of the field name that we use to produce a name for the newly created property according to our naming convention.
Thanks.

Regards,
Zdravko
Telerik
Share what you think about JustCode with us, so we can help you even better! You can use the built-in feedback tool inside JustCode, our forum, or our JustCode feedback portal.
Tags
Refactorings
Asked by
Travis Johnson
Top achievements
Rank 1
Answers by
Zdravko
Telerik team
Share this question
or