Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: it is neccessary to output console.error(error, messages.failedToFix(...)) in catch of autoFixFunc ? #276

Closed
voskresla opened this issue Oct 13, 2022 · 2 comments · Fixed by #277
Assignees
Labels

Comments

@voskresla
Copy link

voskresla commented Oct 13, 2022

With this lines we get additional console error besides the report. When we pass throw null we get this null before default error

console.error(
error,
messages.failedToFix(error, value, nodeProp)
);

'scale-unlimited/declaration-strict-value': ['z-index', { 
    ignoreFunctions: false, 
    autoFixFunc: () => { throw null } 
}],

image

@AndyOGo
Copy link
Owner

AndyOGo commented Oct 13, 2022

That is unnecessary, yes

@AndyOGo AndyOGo closed this as completed Oct 13, 2022
@AndyOGo AndyOGo reopened this Oct 13, 2022
@AndyOGo AndyOGo added bug and removed question labels Oct 13, 2022
AndyOGo added a commit that referenced this issue Oct 13, 2022
@AndyOGo AndyOGo self-assigned this Oct 13, 2022
AndyOGo added a commit that referenced this issue Oct 13, 2022
AndyOGo pushed a commit that referenced this issue Oct 13, 2022
## [1.9.1](v1.9.0...v1.9.1) (2022-10-13)

### Bug Fixes

* [#276](#276) remove console.error ([9f9a59d](9f9a59d))
@AndyOGo
Copy link
Owner

AndyOGo commented Oct 13, 2022

@voskresla
Thanks a lot for the issue.

I removed it an released v1.9.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants