I'm using Rubocop alongside SublimeLinter and we also included it on our continuous integration server, so there is a rubocop.yml on the root of our project.
The file in the root is the one the CI uses to validate the code, but it is not as strict as I want it to be in Sublime.
Is there a way to specify the yml file that I want Rubocop to use in Sublime?
You can set rules in your .rubocop.yml file so sublimelinter works to your new style or if you wish to update the config path use
"rubocop": {
"args": ["--config", "path/to/config.yml"]}
Related
I am trying to use script aliases in the package.json file.
In order for something like this to open the test runner,
"cy:open:prod": "cypress open --env ENV=production",
I run the command npm run cy:open:prod in the command line in the same folder that package.json is located.
The script runs and opens the test runner, however no spec files are found.
In all the examples I have found it describes this approach. Is there something I am missing in configuation to point it to where my spec files are?
Thanks in advance.
There is nothing basically wrong with the scripts in package.json, they look normal and would not cause the problem you mention.
I suggest you check the specPattern setting in configuration, it should match the naming convention you have chosen to use for your specs.
See e2e settings for more details.
Of you still have trouble with it, start a new project and let Cypress set the configuration for you, it will automatically match up the specPattern to the default value.
I have the following problem:
I created configurations to run mocha tests that I want to share within my team. They are stored in *.xml files in runConfigurations folder.
I submit everything except workspace.xml file to the git repo. But when I checkout this project on the clean machine, then the field for mocha path is missing:
I use mocha from my node_modules.
What should I do ?
Also, when I set NODE_PATH for Node.js in Run -> Edit Configurations ... -> Defaults -> Node.js, then this parameter is not saved as well.
Mocha package value is not saved in run configuration .xml, this option is common for all Mocha configurations and thus is stored in workspace.xml as
<component name="NodeJsMochaPackageDirSetting">
<data>path\to\node_modules\mocha</data>
</component>
I’ve succeed to externalize my spring-boot configuration file (application.properties) in a config folder when I run my spring-boot application as a unix service with the help of the official spring documentation https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html
I have also some i18n messages.properties files in my src/main/resources that I would like to externalize in the same config folder but I failed to do it. I’ve tried a lot of things, like playing with spring.messages.basename but unfortunately, it doesn’t work.
I’m using the latest version of spring-boot, and use auto configure mode with the default i18n properties name messages.
What am I missing??? thanks for your help.
Just a few notes:
classpath:message - will always lookup embeded message_xxx files
classpath:/message and classpath:message are equivalent
file:message - will lookup jar's external current directory e.g. ./message_en.properties <- this is what you want
file:/message - you have to put your message files to root "/" to make it work
use notation file:config/message if you need to put in config folder together with your
./config/application.properties
I think you need a leading slash.
Try: spring.messages.basename=classpath:/config/messages
I think, resource bundle is default to classpath. So there's no need to append it. just go straight to your folder location from classpath.
Try this: **assuming your config is inside static folder
spring.messages.basename=static/config/messages
I have a Maven Netbeans Application I want to modify its configuration. What do I need to do to change startup parameters from the conf file like: default_options?
I have to manually do it but would like to make it part of the build process.
You will have to create a netbeans.conf file in your nbm-application project and point the nbm-maven-plugin to it's location - please see http://mojo.codehaus.org/nbm-maven/nbm-maven-plugin/cluster-app-mojo.html#etcConfFile
Create your own ProjectName.conf, for example from default ProjectName.conf file.
Next place it in nbproject folder.
And add to project.conf line like this:
app.conf=nbproject/ProjectName.conf
Support for Custom Configuration Files in NetBeans
When I create a new Compass project, it generates several directories and files and provides the config.rb file. Rather than changing the config file every time I start a project, can I set this up in a existing default file? and where is it?
Take a look at this pull request, it might help: https://github.com/kahlil/grunt-compass/issues/13