-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[CssSelector] Added cache on top of CssSelectorConverter #35425
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
Conversation
lyrixx
commented
Jan 21, 2020
•
edited
Loading
edited
Q | A |
---|---|
Branch? | master |
Bug fix? | no |
New feature? | no |
Deprecations? | no |
Tickets | |
License | MIT |
Doc PR |
d905643
to
5f357e3
Compare
should we use 2 static properties for the cache, or an instance property ? |
Also, the code may be simpler if we define an instance-level |
A New crawler is instanced on each method call (for the results). Then each time you call filter() a new css selector converter is instansiated. That's why the cache is static I will implement your last idea 👍 |
edec12f
to
bdc121c
Compare
Thank you @lyrixx. |
…er (lyrixx) This PR was merged into the 5.1-dev branch. Discussion ---------- [CssSelector] Added cache on top of CssSelectorConverter | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | | License | MIT | Doc PR | Commits ------- ed11d52 [CssSelector] Added cache on top of CssSelectorConverter