-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add Lucee Step Debugger Installation Guide #1447
add Lucee Step Debugger Installation Guide #1447
Conversation
lovely, would you like to link this to the getting started page? https://docs.lucee.org/guides/getting-started/lucee-editors-IDEs.html that page could also be re-prioritised, cfeclipse can be removed, dictionary stuff can the path mappings are trickey and I got stuck myself, the example should include a mapping fo server paths to client paths (i.e. docker), if they are wrong, breakpoints don't stick |
@zspitzer good point! I've tried using |
why close, just update it |
I did update that stuff myself, I'm happy to merge this and then you can do a follow up PR to improve it? |
No need to. I have finished it yesterday, going to do a recheck because I did various changes. Going to update it until tomorrow Another important issue is: I think the latest downloadable version doesn't notify the breakpoints correctly with pathTransform. |
Added and fixed stuff. I've merged the latest master into this PR branch. Now Linter failed with checking some other stuff (outside my changes). I was about to fix those, but didn't want to mix up changes coming from other merges. Letting this here for you to decide how to do it. Hope I didn't add additional work. |
https://docs.lucee.org/guides/Various/lucee-step-debugger-installation-guide.html fixed the linting errors, my mistakes... |
No description provided.