In VSCode, in settings.json for one of my extensions is a line
"extends": "C:/Users/snarl/.vscode/extensions/stylelint-config-wordpress",
But that line is dimmed compared to the rest of the text in the file, as if disabled, or path not found (screenshot). Is that indicating some kind of error I need to resolve? That folder does indeed exist at that location (screenshot).
Motivation For My Question
I ask because this is a line of code I manually added to settings.json, as part of installation instructions for a particular extension. I'm currently using the stylelint extension to help notify me of errors while I type. I am now trying to install a separate extension--stylelint-config-wordpress--which is a set of rules to be used with stylelint. But that new ruleset doesn't seem to be working properly. So I am now trying to troubleshoot why the new rules are not working properly. The settings.json file I edited is part of the stylelint-config-wordpress extension.
Of Note
I am running Windows 10.
When I initially installed stylelint, I installed it globally. I can confirm it was installed properly and linting errors in my code, as expected.
In the GitHub repo for stylelint-config-wordpress, there is one issue related to this (see here). I posted there and received some initial replies. But nothing worked, and I've not heard back since.
After opening an issue in the relevant GitHub repo, I was able to understand the answer to my question.
Short Answer: The code I was adding was incorrect. I was adding:
extends": "C:/Users/snarl/.vscode/extensions/stylelint-config-wordpress",
when I should have been adding something more along the lines of this:
"stylelint.config": {
"extends": "C:/Users/snarl/index.js"
},
Long Answer: If anyone is really curious about how to get this ruleset working in VSCode, you can read this issue.
Related
I have been beating my head for the last 7 hours on this. Full disclosure, I am a PHP guy and not the strongest at ASP.net. So I am coming to you experts.
The issue is that when we run the code below it will product a valid PDF if we use the MSHtmlEngine function (which sets EngineType to MSHtml), but it won't work with the GeckoEngineOptions (which sets EngineType to Gekco). The problem is that the MSHtml won't generate the SVG graphics, so we need to run the Gecko method. When we run the Gecko method, it produces this error:
"ErrorMessage":"Failed to find ABCGeckoWP.exe."
However the file is in the output directory ("bin/"), as well as the project directory. The XULRunner38_0 also appears to be right as well in both the project and bin/.
I am including some screenshots in case it helps / show what has already been tried (sorry for the sizes being all over the place).
You might want to reinstall Abcpdf, from Nuget or reinstall the correct version on the server depending on how it's set up.
ABCGecko cannot function without the XULRunner38_0 folder in the same directory as ABCGeckoWP.exe.
On x64 Windows, even if ABCGeckoWP.exe is found only in %SystemRoot%\System32 (though it should be placed only in %SystemRoot%\SysWOW64 for being 32-bit), it never looks up XULRunner38_0 folder in %SystemRoot%\System32 (but in %SystemRoot%\SysWOW64) because of File System Redirection.
So maybe check the file location as stated above.
This error looks like the version of ABCPdf that you are using and the version installed on the server are not the same.
I would also recommend upgrading the version to the latest one and using the Chrome render engine.
I'm new to developing with Meteor and node-based apps.
I intend to create a PR for a problem i noticed in Rocket.Chat.
I git cloned the Rocket.Chat dev branch and made a change to a certain file:
https://github.com/RocketChat/Rocket.Chat/blob/develop/packages/rocketchat-oembed/client/oembedImageWidget.html
After that i ran the build-script successfully. My build started, but the change is not included.
Using the Chrome Dev Tools to inspect the change, i still see the original unchanged code.
I know it's a rather generic question and i'm sure the solution is kind of stupid, but any idea why ?
Thank you.
Kind regards
It looks like the file you modified is in the packages directory. This is dealt with differently.
Check the .meteor/packages files to see if this package is referenced, if it is, then it will install the package from the atmosphere package management system.
Here the steps required to make your changes work...
1) Edit the .meteor/packages file and change the reference to rocketchat:oembed to be simply oembed
2) Edit the file packages/rocketchat-oembed/package.js and do the same thing, change rocketchat:oembed to be simply oembed
Package.describe({
name: 'oembed',
version: '0.0.1',
summary: 'Message pre-processor that insert oEmbed widget in template',
git: ''
});
I think you can leave the directory names as is.
Meteor will now use your local package instead of going out to get the published version of it
In addition to #Mikkel's answer: I think you don't have to change package name, but just change its version. That should be enough for Meteor to rebuild this package from its source and you won't have any dependency issues.
Am new to Xamarin and is currently building a very simple app using the tutorial from Youtube. Am just in a middle of the video when I got this error even tho I carefully followed all instructions. And even the instructor in the video was able to run his app successfully
Here's the code where I'm getting the error:
var view = inflater.Inflate(Resource.Layout.SignUp, container, false);
For me it is caused by namespace changes. After I corrected the namespace in project properties, then I can build again
I just deleted my newly created axml file, rebuild, add it again, and this time, clean and rebuild.
Everytime I added a new axml file, I clean and rebuild. That's all, thank you :).
Actually this problem occurs when your ResourceDesigner.cs file has not yet mapped the file that you added to your resource directory.
The easiest way i would suggest to handle this situation is you comment the code you are trying to write and clean build your project and it will work like a charm.
Good luck!
In my Resource.Layout.toolbar, Resource was ambiguous between Android.Resource and Xamarin.Forms.Platform.Android.Resource. Instead the one that works for me is [Project name].Droid.Resource. Clean, deleted bin/debug and now it's fine
Resource.designer.cs was excluded from project. Solved by including back.
In Xamarin.Android this problem can be resolved by saving other axml/xml file. Many times cleaning solution, deleting bins/obj doesn't working for me.
In my case my Main file was configured in the Build Action as AndroidResourceAnalysisConfig and then change property to AndroidResource then Build my project and it works.
I had a lot of "XXX" does not contain "XXX" errors like this after a git reverse operation. Very annoying.
I tried all the solutions I could find, all without luck. Finally I magically fixed it by going to the Android project properties, Android Options, then unchecked "Use Fast Deployment (debug mode only)". I then built the project and it worked. Then I went back and checked that option so it was back to normal, and everything is fine.
I have an application that was created from create_react_app then ejected, with no modifications.
Everything works as expected when running the dev version.
Unfortunately when I do npm run build and run this via serve -s build my styles are not working.
The .css files are being found and compiled into a single minified version. But the problem is that the markup that is generated is having the class name prefixes changed to 'T-' instead of the prefix in the compiled .css file. (i.e) MyApp-header is getting changed to T-header, but in the minified css file, it still refers to MyApp-header.
prefix changed to T-
Any help would be appreciated.
This issue turned out to be caused by some nuance of using this...
#SuitCssify.decorator
I was evaluating this library for potential use in a project, and didn't discover this issue until trying to produce an actual production build.
I've since abandoned this approach and changed my configuration to use "CSS Modules" which are working out great. I would provide a link, but my reputation only allows me one link per post. ;(
my 'webpack.config.[dev & prod].js' changes to enable css modules
I accidentally permanently deleted one of my picture files today (it was added to the Qt resource file earlier) through File Explorer (not deleting it via Qt Creator). Now whenever I try to build my project, I keep getting a message that says:
No rule to make target "mypic.png" needed by "qrcfile.cpp". Stop
What can I do to fix this problem ?
So I think I found the solution to this. All I did was clicking Clean all, then Build All, then Run qmake. After those steps, I tried running the project and it worked!