|Bug||"There's something called the "WOLips server", in olden days its purpose was to listen to requests on a certain port, allowing named files to be opened at a specified line number. It stopped working long ago"|
|Bug||Line numbers keep disappearing in WOLips perspective|
|Bug||WOLips reports fake binding errors in large components|
In a Maven project, the New > WOComponent dialog does not honour destination folder chosen by right click. To reproduce:
I regularly trip over this and end up with a new component in the project's root folder. I've already selected a destination folder, because I right-clicked on it. Additionally, I am reasonably sure this works as intended (that is, the right-clicked folder is shown selected by the dialog) in non-Maven projects.
In a Maven project, new .eogen files for EOGenerator are created with inappropriate default destination paths. To reproduce:
When copying an attribute from one model to another in Entity Modeler, the "Prototype" selection (in the "Basic" tab) is dropped. This wouldn't be a huge deal except that subsequently selecting the prototype that wasn't copied then resets every other relevant field in that form to the prototype's defaults. For example:
|Hugi Thordarson||Bug||WOComponent editor: WOLips binding validation isn't case sensitive, but it should be.|
If a binding uses wrong character case for variable names, e.g. "$username" instead of "$userName" WOLips believes the invalid binding is valid, causing errors that can be hard to track down when you're tired and old and you'd rather be outside in the sun doing gardening.
See also: the WOLips github issue list