You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the @override_for decorator only works for top-level domains. However, there are some cases wherein a site has multiple subdomains, usually per country (where each has a slightly different layout). This is due to the current setup of get_domain() (ref).
The problem lies in the following workaround due to limitations of the current @override_for decorator interface:
Closing this issue as obsolete since the new PR in #56 will be able to handle subdomain overrides as it leverages the functionalities of https://github.com/zytedata/url-matcher.
Background
Currently, the
@override_for
decorator only works for top-level domains. However, there are some cases wherein a site has multiple subdomains, usually per country (where each has a slightly different layout). This is due to the current setup ofget_domain()
(ref).The problem lies in the following workaround due to limitations of the current
@override_for
decorator interface:Objectives
I'm wondering if it's worth it to update the current interface with something like this?
Depending on the situation, this provides another option on how to structure the collection of PageObjects in the project.
The text was updated successfully, but these errors were encountered: