Skip to content
New issue

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

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

Already on GitHub? # to your account

refactor: corrected some aspects out of eslint feedback #1399

Conversation

mfranzke
Copy link
Contributor

@mfranzke mfranzke commented Dec 25, 2021

Summary of changes:

Fixed some of the aspects that comes out of eslint feedback (via yarn lint).

@mfranzke mfranzke marked this pull request as ready for review December 25, 2021 23:45
@mfranzke mfranzke requested a review from sghoweri as a code owner December 25, 2021 23:45
@JosefBredereck
Copy link
Contributor

Do we need the commented-out code, or can we remove it entirely?

@mfranzke
Copy link
Contributor Author

mfranzke commented Dec 31, 2021

Do we need the commented-out code, or can we remove it entirely?

@JosefBredereck I was struggling with this question as well. I decided to leave it in as we don't need it at the moment, but as soon as someone might need e.g. the event or options parameter, they could even already follow the naming (pattern) and don't need to look this up. But that's the only small reason that I came up with that pulled me into the "leave it in direction", whereas I'm fine with both ones, so I could still remove them. What do you think?

@mfranzke
Copy link
Contributor Author

Do we need the commented-out code, or can we remove it entirely?

I've just decided to remove them. So we should be good to go now.

@JosefBredereck JosefBredereck merged commit 97f1964 into pattern-lab:dev Jan 1, 2022
@mfranzke mfranzke deleted the refactor/corrected-some-aspects-out-of-eslint-feedback branch January 1, 2022 17:01
@JosefBredereck
Copy link
Contributor

PR was released with v5.16.0

antonia-rose pushed a commit to quelltexterin/nemo-uikit-workshop that referenced this pull request Apr 12, 2023
…1399)

* refactor: fixed 'warning  'data' is assigned a value but never used  no-unused-vars'

its usage has been removed with pattern-lab@70fe9b6#diff-75bedd8b06cebb50236c7c659b539b0fa984746f8abb3d7a5dc6a92b3763fcc0

* refactor: fixed "warning  'event' is defined but never used          no-unused-vars"

* refactor: fixed "warning  'NodePart' is defined but never used                 no-unused-vars"

This isn't in use anymore since commit pattern-lab@2ff8e1c#diff-b26f09ed0fc0febb6d869ff60e410d9d8efd300b4b6c2facbf668cd4555e27a2L39

* refactor: fixed "warning  'customElement' is defined but never used  no-unused-vars"

* refactor: fixed "warning  'previousValues' is assigned a value but never used  no-unused-vars"

as its usage hasn't been in use since commit pattern-lab@2ff8e1c#diff-b26f09ed0fc0febb6d869ff60e410d9d8efd300b4b6c2facbf668cd4555e27a2R45

* refactor: fixed "error  Method 'slotify' expected a return value  consistent-return"

* refactor: fixed "warning  'unsafeCSS' is defined but never used  no-unused-vars"

and css and svg as well

* refactor: fixed "warning  'event' is defined but never used  no-unused-vars"

* refactor: fixed "warning  'event' is defined but never used     no-unused-vars"

and filePath as well

* refactor: fixed "warning  'pm' is assigned a value but never used  no-unused-vars"

as its usage has been removed with commit pattern-lab@deb4783#diff-25426a917b53575c0f0efc5674ee70c4d2c8671f9ade4f9d994db43c9552302bL217

* refactor: fixed "warning  'options' is defined but never used  no-unused-vars"

* chore: removing the previously out-commented parts
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants