[ANN] PropertiesEditor Plugin 1.6 Follow
Changes:
Rename property refactoring(Shift+F6 on property name, works only in properties files for now). Experimental use with care! Feedback is highly appreciated.
Navigation tree state saving(expanded nodes)
Reported bugs fixed and small improvements provided
TIA,
Dmitry
Please sign in to leave a comment.
Feature request: different icons for "folders" which have a property value attached.
example:
a.b=foo
a.b.c=bar
a's icon should be a "normal folder" (such as now)
b's icon should be a folder with a superimposed sheet
c's icon should be a sheet (such as now)
Of course the rename working only in property files is not much useful: if the rename does not touch java and jsp files nearly all usages of the property become broken!
Hi,
It's just beginning wait please :)
TIA,
Dmitry
This brings the following interesting question to the table:
What happens when you rename a.b? The user should probably get the option to
rename everything recursively or not, i.e. rename only a.b or also a.b.c,
a.b.c.d, etc.
Amnon
"Davide Baroncelli" <baroncelli@yahoo.com> wrote in message
news:29073934.1082714798178.JavaMail.itn@is.intellij.net...
attached.
>
>
>
>
the rename does not touch java and jsp files nearly all usages of the
property become broken!
Yes, I thought about this and... decided I am too lazy to decide what is the best solution! ;)
I think it should be presented as a check-box to the user or as a list of
potential things to change with All / None buttons and checkboxes.
Taking a flat property file and turning it into a tree is great, but if the
file existed before (like ours) it was treated as a flat file, even though
in many cases the tree representation makes sense because of naming
conventions etc.
Amnon
"Davide Baroncelli" <baroncelli@yahoo.com> wrote in message
news:17925002.1082737218205.JavaMail.itn@is.intellij.net...
the best solution! ;)
Hi,
"Potential things" is properties deep to hierarchy?
How plugin can help you to turn your flat files to tree-like properties naming?
TIA,
Dmitry
Yes.
For example, the plug-in can detect various naming conventions and suggest
unifying them.
For instance, if in a properties file there are:
myFirstProprty
some.other.property
YET_ANOTHER_ONE
The plug-in, according to the preferred "property file code style" suggest
to unify the code style.
Let's assume that the preferred code style is small letters separated by
dots.
The suggestion would be to rename myFirstProperty to my.first.property and
YET_ANOTHER_ONE to yet.another.one.
Amnon
"Dmitry Kashin" <no_mail@jetbrains.com> wrote in message
news:1374313.1082747969410.JavaMail.itn@is.intellij.net...
>
naming?
>
Hi,
Icons request implemented.
TIA,
Dmitry
This name suggestions must be in rename dialog as well?
About automatical detection I'm affraid it very difficult to implement :(
TIA,
Dmitry
Nice plugin. Dmitry.
One request - please enable ALT-F1 - View | Select in.
Thanks,
Ken
Dmitry Kashin wrote:
Not really, just collect statistic about different conventions used in
the property file (check delimeter: it can be '_', '.' or
'$CAPITALLETTER'), sort it and choose the top one. Rest modify
respectively. Very easy to write unit-test thus very easy to code.
Sergiy
Hi,
I mean not detection but presentation of it. It must be kind of inspections but I don't know how to make more like "IDEA".
TIA,
Dmitry
Intention would be a good place.
sergiy
Hi,
Using intentions for batch operations is not good idea, there must be some kind of inspections for this feature, I'm think.
TIA,
Dmitry