Option to skip Addon dependencies
See original GitHub issueOne addon is offending with bare-strings
, the error is caught during our main app build:
bare-strings: Non-translated string used (modules/ember-formly/templates/components/ember-formly-component-unknown @ L1:C5):
`Ember Formly: Unknown Component`
===== 1 Template Linting Error
Is there a way to skip linting addon dependencies?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Maven – Optional Dependencies and Dependency Exclusions
Optional dependencies are used when it's not possible (for whatever reason) to split a project into sub-modules. The idea is that some of...
Read more >Maven Dependency Plugin command line option to ...
My requirement is just to find & download all dependencies (including transitive) for specific libraries that i wish to upgrade. I found maven's...
Read more >Issue #61 · pmckeown/dependency-track-maven-plugin - GitHub
Maven plugins commonly have a skip option to allow for the disabling of the plugin execution. Add one to this plugin.
Read more >Downgrading versions and excluding dependencies
A dependency version can be enforced by declaring it as strict it in the build script: Example 1. Setting a strict version. Groovy...
Read more >yum problems: Skip Packages With Broken Dependencies ...
You need to add plugin called yum-skip-brokenm which adds a ... extras: mirrors.liquidweb.com Setting up Install Process Parsing package ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One thing that is a definite “gotcha” with NPM packages is that
npm pack
andnpm publish
use your local working copy to build the tarball sent up to the registry, this means that any dirty files are packed as they were locally during publishing (and they can differ from what is checked into source control).In general ember-cli-template-lint does not lint addon modules, but occasionally addon authors forget to remove
isDevelopingAddon
overrides when publishing. When that happens the addon’s templates would get linted as you are seeing here…