scss-lint - how config the default.yml? - gulp

I'm using scss-lint with gulp.js in my project and I want to add some configurations to my local scss-lint fork.
In the documentation of scss-lint it's says that I can add a configuration by creating a file named .scss-lint.yml in the styles directory, so I do:
scss_files: 'src/styles/**/*.scss'
NestingDepth:
enabled: true
max_depth: 4
SelectorDepth:
enabled: true
max_depth: 4
But when I run gulp the configurations just not apply. How can I make my configuration work?

Be sure to place your .scss-lint.yml config file either in the root directory of the working project for local use, or indeed in your Home Directory for global use.
To find the path of your Home Directory you can reference this list.
Using scss-lint with Sublime Text?
Be sure to restart the Sublime Text to activate your .scss-lint.yml config file.

Related

Pylint nested pylintrc : Specify a configuration file

Goal
I want to use pylint without specifying the file path (just run pylint instead of pylint --rcfile=linter/.pylintrc), as I want to save all linter related files in a subfolder linter/.
I thought of adding a .pylintrc file at the root folder only a redirection to the actual config file linter/.pylintrc.
Exploration
The option rcfile seems to be what I look for, it doesn't seems to import the settings from the sub-folder. What am I missing ?
Proposed .pylintrc file for redirection:
[MASTER]
# Specify a configuration file.
rcfile=subfolder/.pylintrc
This is not supported in pylint see this pull request

PhpStorm Xdebug how do I configure path mapping for full folder

I have this setup that one plugin in my project is symlinked to a different folder on my local machine.
Something like this:
/Sites/MyWebProject <-- contains application and PhpStorm project
/MyPlugins/MyCustomPlugin <-- contains my custom plugin that I am working on.
/Sites/MyWebProject/plugins/MyCustomPlugin --> symlinked to: /MyPlugins/MyCustomPlugin
Now when I run Xdebug and add a breakpoint PhpStorm will open the symlinked file. Then I can add a 'path mapping' and this file will be recognised as expected.
My issue is that I want to setup the 'path mapping' for the whole directory. And not on a 'per-file' base.
Is this possible?

Missing fonts folder on jekyll deploying to netlify

When deploying jekyll project to netlify I am missing my fonts folder.
It works perfectly find when in development mode but when I tell it to run in production it seems to skip over adding my fonts folder to the _site/assets directory.
I believe it has to be something in the config but I am fairly new to jekyll and YAML. And in the code its seems to be saying to add all the assets underneath it to the build process.
Below is my _config.yml file.
copy:
# Paths to static assets that aren't (S)CSS or JavaScript
# because these are completely handled by the sass and javascript tasks
assets:
# all files below the assets dir
- "assets/**/*"
# exclusions:
- "!assets/{js,scss,css}/**/*" # js, scss and css files
- "!assets/css{,/**}" # css dir
- "!assets/js{,/**}" # js dir
- "!assets/scss{,/**}" # scss dir
- "!assets/vendor{,/**}" # vendor di
dist: "_site/assets/"
notification: "Running Copy"
Note: I work for Netlify
While I'm not sure of the fail mode here, I can tell you a couple things that would help you debug:
the easiest way to debug a build is described in this article: https://www.netlify.com/blog/2016/10/18/how-our-build-bots-build-sites/ . This lets you duplicate our build environment in a way that you can access during/after the build so you can see what is happening or has happened in more depth than our build logs
If you write into support we can set a verbose flag on your builds that does the equivalent of 'set -x' on the building shell script to show you what's being run in production, though filtering this output is quite a task for a human, it may be more useful than nothing!

PhpStorm: how to use project root variable or relative path in PhpUnit configuration?

I would like to setup PhpUnit in PhpStorm. I press 1. Edit Configurations... and would like to enter this parameter in field 2.
I am using phpunit.xml as configuration file and all want to use a relative path like:
phpunit.xml
or use project root variable like
$PROJECT_ROOT/phpunit.xml
But both options are not working for me.
Based on your screenshot (the place where you want to use it): use full path -- in project settings such path is stored relative to the project root anyway (unless you specify some file which is outside of the project, of course) and the full path then reconstructed when needed (e.g. when shown to you or when used as a parameter during tests execution).
I don't think you'll be able to achieve what you want via the project's Run/Debug configurations. What might help you is the Default configuration file setting in your default project settings, which can be used to define the PHPUnit configuration file to use by default, so you don't need to specify it via the Use alternative configuration file option in your Run/Debug configuration.
To set this, open your Default Settings window, then navigate to Languages & Frameworks -> PHP -> PHPUnit. In the Test Runner section tick the Default configuration file checkbox and specify the location where you keep your configuration file. If this file will always be in the same path relative to your project root, you can use the $PROJECT_DIR$ variable to define the project root. So if your PHPUnit configuration file is always in the root of your project, you might set this to something like $PROJECT_DIR$/phpunit.xml. When you create a new project, its Default configuration file variable will be set to the file offset from your project root, and you won't need to use the Use alternative configuration file option in your Run/Debug configuration.
If you're opening the same project in different locations on the same machine this should work for new projects without any problem, if you want to share this configuration across machines, you might need to try PHPStorm's Exporting and Importing Settings functionality.
I'm not sure if this directly solves your problem, and it's a few months late anyway, but maybe this will be useful for someone else who stumbles across this question... The above instructions were correct for my 8.0.3 installation on Linux.

How to install MySQL Connector/C on Mac OS X?

I'm writing an app in C that requires MySQL interaction, so I downloaded the Connector/C archive from the official website, and it contains bin, lib and include folders, but I don't know where to install them.
I could copy the include files into my project folder, but where can I put the lib file so that my compiled binary (and other binaries) can find it?
Thanks in advance!
This is confusing, isn't it.. don't know why they don't make this more clear.
The lib/ files go in /usr/local/lib
The include/ files go in /usr/local/include
The bin/ files go in /usr/local/bin
The /usr/.. directory isn't visible through finder afaik so you have to go at it via commandline. Best of luck
Also, in your Xcode project, make sure you add a Linked Library by going to your Target's settings, General, then adding Linked Library "libmysqlclient.dylib"
Alternatively, to do everything on the commandline by "mv", you could also execute (on cmdline):
defaults write com.apple.finder AppleShowAllFiles TRUE
and
killall Finder
to make the hidden folder /usr (and everything else) visible.
After placing your connector files (like Nektarios explicitly discribed where) and closing all "hidden folder - finder windows", execute on your cmd:
defaults write com.apple.finder AppleShowAllFiles FALSE
and again
killall Finder
to hide what have to be hidden.