Conversation
ybiquitous
left a comment
There was a problem hiding this comment.
@mattxwang Thank you for creating this pull request! I think the implementation is in the right direction. 👍🏼
jeddy3
left a comment
There was a problem hiding this comment.
@mattxwang Looking good so far!
I've requested a few changes in addition to @ybiquitous'.
Co-authored-by: Masafumi Koba <473530+ybiquitous@users.noreply.github.com>
Applies suggestions from code review: - removes invalid CSS from docs and test cases - removes redundant docs entries - uses `a` for all selectors - writes a new helper "isValueNode" to cover word, function, string value types - adds new test case for css variable
…operty-max-values
4701a2f to
7955ad1
Compare
|
Thanks for the in-depth feedback @jeddy3 and @ybiquitous, it's much appreciated - I still have a lot to learn in terms of the codebase and best practices. In general, I think I've addressed each point of feedback. I did have a chance to implement And, anything else I should be mindful of? |
|
@mattxwang I think your implementation of |
jeddy3
left a comment
There was a problem hiding this comment.
Thanks for making the changes! Looking good.
In addition to @ybiquitous' suggestion, just one more minor request from me
Co-authored-by: Masafumi Koba <473530+ybiquitous@users.noreply.github.com>
|
Thanks for the suggestions @ybiquitous, didn't realize that we'd get better typing by importing from @jeddy3, I may be missing something, but what was your requested change? I don't see anything attached to your "requested changes" dialog box. |
ybiquitous
left a comment
There was a problem hiding this comment.
@mattxwang Thank you for addressing the reviews. Almost good. 👍🏼
I've left more trivial suggestions and one question.
Moves `validateOptions` outside of `walkDecls`, better type annotation style! Co-authored-by: Masafumi Koba <473530+ybiquitous@users.noreply.github.com>
ybiquitous
left a comment
There was a problem hiding this comment.
@mattxwang Thank you for implementing the excellent rule. LGTM 👍🏼
Moves external require to top of require list Co-authored-by: Richard Hallows <jeddy3@users.noreply.github.com>
|
Completely missed one of the requested changes, my fault! Should have addressed all the comments - @jeddy3 let me know what you think! |
jeddy3
left a comment
There was a problem hiding this comment.
Thanks for making the changes. I think the tests and readme work better now.
LGTM.
|
Closes #5435, related to #3968.
As suggested by @jeddy3, I've scaffolded this off of
declaration-property-value-allowed-list. I've also implemented a new util,validateObjectWithProps(), and written some tests.This is my first time creating an entirely new rule, so I have three things I'd like to get some feedback on:
validateOptionsutility function. How should I use it here, if at all?wordnodes after running the value through the value parser. Is this the correct approach?