Arjuna

- Support for axes locator
- Added axes locator and made minor doc edits for name of app in GuiAuto chapter.

Following are the significant changes since last release:

- Support for OR relationship among different values of same locator type - coded as well as GNS.
- Support for Visual Relationships
- Coded - Added at App/Page level.
- GNS Support added - Can provide label from same GNS file.
- Coded - widget call can be used to provide as relationship rather than existing element.
- GNS supports chain of relation: label1 -> label2 -> label3
- When multiple locators are provided with an OR relationship, relations are applied to each one of them.
- In GNS the relationship labels can contain Arjuna placeholders and then the parent label can be formaated as usual using gns.formatter call.
- Nested element finding falls back to direct finding with WebDriver as JS execution support exists only at driver level in Selenium.
- with.JS and With.Point is supported at element level, however it does not do nested element finding, rather uses driver itself.
- The fallback mechanism for JS, Point and Relative locators has been added so that such locators can be defined without issues in GNS files or coded GuiSections which have root element set for them.
- 'pos' meta key in widget meta data:
- Supported in coded as well GNS format.
- Supported in nested element finding.
- Value can be an int, a list, an extractor string literal, an extractor specification dict or an extractor object.
- Docs added for additional OR support, Visual Relationships and position filters
- Rearranged locator docs to place coded and GNS entries next to each other.
- Added GuiWidgetDefinitionError as an exception to TPI.
- Added support for .local files for the following: (if present these files override the corresponding regular config files.)
- project.local.yaml
- data.local.yaml
- envs.local.yaml
- sessions.yaml, stages.yaml, groups.yaml
- Support for empty sessions.yaml, stages.yaml and groups.yaml. Named exception raised rather than NoneType exception.
- Added explicit requirement for urllib3

- Support for bases in Data Entity - building a data entiry from other data entities.
- Added doc for YAML's handling of boolean strings.
- Added tests and docs for Data Spaces.

This build introduces positional placeholders in withx, improved attr() call, easier support for attr names that conflict with Pyhon keywords.

- Support for anonymous/positional $$ placeholders in withx extended locator definitions.
- attr() call now accepts a single key-value pair instead of two positional arguments. Conflicting Python name is prefixed with two underscores (__)
- node() call simplified. Conflicting Python name is prefixed with two underscores (__).
- Updated Locator Docs to reflect the above improvements.
- Fix in GuiDropDown logic - changed 'tag' to 'tags'.
- Added TPI exceptions to global import.
- Fix in attr locators used in withx

Updates available in this release:

- node Locator
- Converts to Xpath or CSS Selector based on condition of text matching (text or star_text or dot_text)
- Added provision for star_text which converts to *//text() instead of text() for specified text. It can also be specified as *text.
- Added provision for dot_text which converts to . instead of text() for for specified text. It can also be specified as .text.
- tags support is added to define multiple tags which are treated as a relative sequence of tags. Either tag or tags should be used. tags can take a single tag, multiple space separated tags as well as a list of tag strings.
- classes support is added to define one or more classes as string or sequence.
- tag locator changed to tags
- Is converted to CSS selectors
- The tags can be provided as space separated tags string or sequnce of tag strings.
- When more than one tag is supplied, the sequnce is assumed to be a descendant sequence (not immediate children)
- Docs updated and improved for locators.

Updates available in this version:

- Support for 'node' as a valid selector (with type)
- Can be used programmatically in calls e.g. element(node=node(**kwargs))
- If the names of attrs conflict with python keywords (e.g. for), you can also provide an 'attrs' dict: element(node=node(a=b, attrs={'c' : 'd'}))
- The values in attrs dict are overriden by the direct kv paris supplied in node call.
- 'tag' is a special key and represents the tag name of the node and is not treated as an attribute.
- 'text' is a special key and represents the text content of the node and is used for matching.
- node represents partial match for attribute contents, bnode partial match at beginning of attributes contents and fnode represents full content of node attributes.
- There is an AND relationship among all attribute values supplied.
- You can use formatters to format the '$$' placeholders within keys and values of node, bnode and fnode.
- These selectors can be used in GNS files just like other selectors.
- Updates in Attribute related locators.
- Change in the way attr, fattr are specified in code and GNS. Breaks current usage.
- Rather than name and value arguments, direct value will be supplied as key value pair.
- Specifying tag in the definition will not be supported.
- node selectors will support tag and multiple attributes to bridge this gap and provide more advanced functionality.
- battr, eattr support
- attr related locators are converted to CSS Selectors instead of XPath.
- Withx Enhancements
- Withx can be used to define custom locators using node, bnode and fnode. Placeholders and kwargs work for attr names as well as values.
- Withx supports $$ placeholders like normal GNS.
- Withx suports C,L,R placeholders.
- Name changes: Attr -> attr, NVPairs -> nvpairs
- Comprehensive documentation of locators in coded and GNS formats along with withx documentation.
- More information in exceptions that are raised when linked projects represent wrong paths.