-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build #25
Build #25
Conversation
Intercept and reformat compiler errors by subclassing ExecCommand
Proxy to external plugin if installed otherwise inform user
Mirror sublime.expand_variables syntax. But sublime functions would make code less clear here. Revisit for ST2 compatibility
Read and write build settings with intelligent defaults
Enable custom builds instead of compiling without output. Fix empty compile on Windows
Tried it out, got this in the console:
I've seen the
...but this time it didn't help. Anyway, the error was happening because the file I was editing (
...although naturally that's not a scalable solution. 😄 |
At that point the build ran and I saw the output in the console, which was pretty sweet! I have Highlight Build Errors installed, but didn't see any inline. (I also tried uninstalling/reinstalling Highlight Build Errors, uninstalling/reinstalling Awesome progress @dnalot! 😃 |
Mind reporting each in my fork?
|
Status:
|
Integrate SideBarEnhancements for ST3 for poplarity and browser detection
Also appears in Tools menu
Load external dependencies lazily. Flip of the coin whether they error otherwise
Fix import for execCommand. Lazily load Highlight Build Errors c.f. previous commit
Parse plain string lines interspersed with JSON from elm-make
I just remembered this, and so I don't forget it I'll write it down. the |
I already did it. Don't merge yet though! I just rebased. |
Remember kids, don't try this at home
@rtfeldman All issues should be fixed 🙏 |
...because I over-engineered it
Is it possible to hyperlink from errors in the console to the code? |
That would be very nice, if possible! On Thu, Aug 6, 2015, 12:05 PM Pete Vilter notifications@github.com wrote:
|
Yes but I'm still evaluating how to do it with the least amount of code. Basically it's completely custom navigation. Report it in either repo and I'll tag it as a feature! |
Reported in your fork (issue 3) |
- Conventional property naming - Fix ST2/3 incompatibility - Log decoded elm-package.json
Also simplify common imports
Because this took hours to diagnose myself
Maintain key order in elm-package.json for diffs and log JSON key paths
Beware: MRO currently broken for patched methods
Build system file_regex only navigate single lines. In the future we could provide an enhanced double click handler
@deadfoxygrandpa This one's ready to merge. I'll open a separate PR for a ST3 error in existing code. Also looking into #28 if you can take #29? |
OK, I'll merge it in. Thanks a lot for all this work. |
This is the big one. I'll just list features:
Run
additionally builds output to an intelligent path.elm-package.json
. Keys not documented? No fear! There's a UI labeledElm Build System
in the Command Palette. It only requires a valid config in any ancestor directory of the edited file.