Java: Is it bad practice to write methods that start with "get" when they aren't getters?

With these it helps The "default" access does not guarantee much of anything, since any rogue programmer can declare their class in your package. Also, regardless of your package structure, in java, you almost always can do an "instance of" check, and then downcast to the "instance of" type. So, if your goal is to prevent any downcasting whatsoever, you must use the private keyword. For example, you can declare the concrete implementations of your Product interface as private static or as anonymous inner classes within your Factory. Indeed, in Bloch's "How to design a good API" article, he makes a point that you should "Minimize Accessibility of Everything."
That said, I think you're being a little paranoid here. Does it really matter that much to you if somebody downcasts? Any code that you write can be misused, and certainly if you include a well-documented factory then you have provided clear information about how to use your API properly. Also, if you build a real factory method that takes arguments and has clear method names, as opposed to this toy Factory example that takes no arguments, then I think you'll find that you're broadcasting the publicly relevant part of what's being created anyway.

around this issue I have next code:

I hope this helps . Getters don't have to specifically map to a backing field. They only have to do what they say they do: return a value that is somehow contained within that class.
This says nothing about the way this value is stored. This can be either directly through a backing field or it can be through a lookup in a collection or it might even outsource this behind the scenes to some sort of data provider.

wish of those help The issue is you are putting the "," for the decimal separator. Most programming languages are ASCII and English, so you must use the "." for the floating point value.
The Java compiler is confused by the comma, thinking you might be putting a list where you cannot actually put a list.

I think the issue was by ths following , This is what worked for me, despite what you did being the example Vuex uses in the documentation.
Use