Make links in stylelint report in bash output clickable - bash

I am using stylelint and eslint and I just mentioned that it is possible to click on a line in eslint to directly open the file in my IDE and jump to that selected line.
I was wondering if it is possible to add a similar feature to stylelint since this is not possible by default:
I already tried to fix this, but I cannot find a track that feels good. Can you recommend a way to do this? Is this something that should be changed directly in the source code of stylelint or should it be written as plugin? And if yes, is there any plugin that already modifies messages that I can use as example/reference? Or does this feature already exist and I was just not able to find out how to enable it?
Another idea of myself was to pipe/pass the output of stylelint to another script to then be able to use some regular expressions to replace the lines with hyperlinks like described in Terminal - create hyperlinks, but I think there should be a less hacky way to resolve this.
Looking forward to some tips where I should dig deeper, thank you in advice!

Related

Two different coding standards

I would like to know if there is a way to work on one C# code standard but before committing the code change the format of the files to a different one in Visual Studio 2017.
I like to work with braces in the same line but would like to, once I'm done, update all the files to use braces on a new line before committing the code to source control. Also, I would like the ability to open the files I need to work with and have them formatted the way I like them
Is there a way to accomplish this without importing different settings before committing the code?
Thank you,
I am using prettier. Together with pre-commit tools like husky, you can reformat the code during the commit.
I don't know if you can define a custom format during coding beside of prettier or give prettier a diffrent config for coding and committing, but perhaps you give it a try.

Cucumber - How to run tags or feature files based on the pom/goal?

I have all my scenarios properly tagged and working.
I am trying to set it up so that depending on the goal that is set, only specific tags or feature files (whatever is possible) run.
I've looked at other related questions but didn't find one that seem to work for me.
I don't need to put anything conditional in as I've seen in a previous question that's not easily doable.
I did see in another question they found a way of doing it my making a Cucumber.Run super class and passing in the needed options then but there weren't further details.
And recommendations would be great.
I tried using various profiles/builds to exclude all but the desired feature file but Cucumber.Run seems to ignore that after my research.
To make it clear, basically I have:
File1.feature
#scenarioForFile1
----------------
File2.feature
#scenarioForFile2
----------------
File3.feature
#scenarioForFile3
And I need to control which set of tests is kicked of either by scenario or file name.
After another day of research I was able to find the answer and feel stupid because I've looked at the usage docs several times but thought I couldn't do what the example showed in my use case.
Now I just have various build set up that run the project using different tags in the command line argument. I thought it was necessary to use the pom but it was not.
Used the below two links:
https://github.com/cucumber/cucumber/wiki/Tags
Maven running cucumber specific feature files or folders

How to Hide the source code in xcode?

I am writing an app using applescriptobjc in xcode, and while making the archive I see the source code is still inside the package, is there a way to hide it or transform it completely to binary code?
Thanks
I may be a year late to the discussion but I asked the same question around the same time as you did last year and hope that the answer I got will satisfy your own question. Here is an extract answer from
my own question:
When you save the AppleScript file you have the option of checking "Run Only" - in that case the script is compiled into a new form that can be run exactly as the original script, but it is not meant for further editing/development.
It doesn't mean that the run-only file is complete protected or non-readable, but parts of your code, comments, etc. are not included or not easily readable.
If you want to do more you'll need a code obfuscator if you still want to use AppleScript - however I'm not sure if one exists on the market, or you need to develop your own.
As you can see, a simple way to do this is:
Open your final AppDelegate.applescript file in Script Editor on the mac.
Select: File > Export...
2.1. Don't change the file name but override the archive file
2.2. BEFORE SAVING: Choose Run-only checkbox from the save options but leave the File Format as Script
Now your file cannot be opened in plain text as it is set to Run-only. Please remember that it is not a 100% read-proof solution, but works great for small projects (provided you are not rushing the final export and don't forget to perform the above mentioned steps before handing it over to the customer).
I hope you can make the most of this answer and still deem it useful. Let me know how you get on or whether you have any more questions. Perhaps you have since found a far better solution (or just an alternative), if so, I am still looking for the next best thing in source code protection.
In Xcode 9.2. (and maybe earlier versions) you can find under Build Settings the item OSACompile and can choose to compile to an executable only directly from Xcode.

How to find a work-around when Xcode analyzer finds issues but does not show them in the files?

I'm having trouble with Xcode 4.5.2's analyzer. It is able to find issues:
But, while the issues are displayed on the top bar:
,
the issues are not shown inside the file editor. Without this information, there is no practical way to know what the analyzer was talking about.
Is there a log file somewhere where I could find a line number for the detected issues? Any other workaround or setting tweak?
The only workaround I can think of is running the analyser from the command line. That can be done directly on Xcode projects (ie, no makefile barbarism required) and should give you direct textual feedback.

Running Macro in Notepad++ from Commandline

Is it possible to run a Macro which i record in Notepad++ from the Commandline? Say i record a Macro to search and replace, which i can run in Np++ for the whole text file, i would like to do this kind of Job in a Shell file, is this possible? I couldnt find anything about this in the Documentation.
If not possible can anybody recommend alternative easy to use porgrams for this kind of Job?
Thank you
I haven't seen any documentation on doing this in Np++, but I am pretty sure you can do it in UltraEdit. This is not a free product, though.

Resources