cclose1 commented on issue #8953: URL: https://github.com/apache/netbeans/issues/8953#issuecomment-3455522473
Hi Matthias I accept that from the point of view of Netbeans, other than writing code to check the validity of the js file, there is nothing that you can do. I think the problem is with Javascript itself, but I don't know who, if anyone, would be interested in solving it. The following are some final observations. I checked the war file and the relevant js is in it, so I guess that the behaviour is down to the browser code. I use Chrome, but when I ran it on Microsoft Edge, the same thing happened. This feature makes use of private variables almost a waste of time. I now have an approach to finding the code error. If it is not obvious from code inspection, I comment out the body of the class and decrease the commented out area until I find the line that triggers the failure. I tried this recently and the error was that in a 7 character identifier, I'd typed an s instead of a. When you are looking at many lines of code such errors are hard to spot. The thing that really surprises me is that, apart from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_elements. I've never seen anything to suggest private variables exist. I've seen lots of java class code examples and I don't recall ever seeing one used. Lots of use of __var, which is the convention for indicating a private variable. Never seen anyone complaining about a problem with them. I'm beginning to think that I'm the only one using them. Can that really be the case? The pragmatic thing to do is to stop using them and switch back to using __. From a purist point private class members and variables are appealing. From my perspective this issue can be closed. Thanks for your prompt responses. Regard Chris On Sun, Oct 26, 2025 at 7:13 AM Matthias Bläsing ***@***.***> wrote: > *matthiasblaesing* left a comment (apache/netbeans#8953) > <https://github.com/apache/netbeans/issues/8953#issuecomment-3448080963> > > Given that private class properties were introduced about 2023, perhaps the > handling of them has not been fully worked out. Failing to generate the js > file is a less than helpful response. > > YOU wrote the file. Nothing is generated at that point. The only thing > NetBeans can do is tell YOU that the code YOU wrote is wrong. That indeed > would be helpful, but is not implemented yet. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/netbeans/issues/8953#issuecomment-3448080963>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABGZF24NQB6RSGFI6GEQNQT3ZRRCJAVCNFSM6AAAAACKE5KFJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBYGA4DAOJWGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
