Daydream generates extreme selectors about daydream HOT 8 OPEN

@kokujin Do you have a better idea for ensuring a unique path to the element? I'm sure there's a smarter way to do it, just haven't had time to think it over.

from daydream.

Maybe it would be smart to introduce a configuration where you can specify how the selectors will be calculated? With options like:

• the dept of the selector - something like up to lvl 3 parents, etc.
• list of classes to ignore
• ignore parents at all if there is an id attr

from daydream.

I think that would open a can of worms @michalbe , It would be best it it would just automatically generate the shortest, most optimized selector.

Think about the scenario of allowing non technical users in a QA department.

from daydream.

Have you thought about using a third party lib to generate the electors @stevenmiller888 ? for example, https://www.npmjs.com/package/css-selector-generator, from the description:

it also generates shorter selectors and is faster and/or more robust than many other libraries - see this comparison and select the best alternative for your use case.

from daydream.

https://github.com/autarc/optimal-select is also an option to generate short selectors

from daydream.

Not sure if the first one is a good choice, apparently the lib has some infinite loops bugs inside.

There is a benchmark for this already: css-selector-generator-benchmark

from daydream.

RE @michalbe I'd love to also specify a black list of selectors.
A few "bad" selectors mess really mess my tests up.

from daydream.

@stevenmiller888 the pull request #32 has already solved this and I think this can be closed. In all my testing I haven't experienced any issues with long selectors.

from daydream.