@mariusandra/simmerjs
Version:
A pure Javascript reverse CSS selector engine which calculates a DOM element's unique CSS selector on the current page.
48 lines (40 loc) • 1.99 kB
JavaScript
;
Object.defineProperty(exports, "__esModule", {
value: true
});
exports.default = _default;
var _queryEngine = require("../queryEngine");
var _validationHelpers = require("./validationHelpers");
/**
* Inspect the elements' IDs and add them to the CSS Selector
* @param {array} hierarchy. The hierarchy of elements
* @param {object} state. The current selector state (has the stack and specificity sum)
*/
function _default(hierarchy, state, validateSelector, config, query) {
return hierarchy.reduce((selectorState, currentElem, index) => {
if (!selectorState.verified) {
const [validatedState] = [currentElem.el.getAttribute('data-attr')].filter(id => (0, _validationHelpers.attr)(id)).map(dataAttr => {
const isUnique = (0, _queryEngine.isUniqueDataAttr)(query, dataAttr);
selectorState.stack[index].push(`[data-attr='${dataAttr}']`);
selectorState.specificity += isUnique ? 100 : 50;
if (selectorState.specificity >= config.specificityThreshold) {
// we have reached the minimum specificity, lets try verifying now, as this will save us having to add more IDs to the selector
if (validateSelector(selectorState)) {
// The ID worked like a charm - mark this state as verified and move on!
selectorState.verified = true;
}
}
if (!selectorState.verified && index === 0) {
// if the index is 0 then this is the data-attr of the actual element! Which means we have found our selector!
// The ID wasn't enough, this means the page, this should never happen as we tested for the data-attr's uniquness, but just incase
// we will pop it from the stack as it only adds noise
selectorState.stack[index].pop();
selectorState.specificity -= isUnique ? 100 : 50;
}
return selectorState;
});
return validatedState || selectorState;
}
return selectorState;
}, state);
}