[pull] master from robotframework:master#145
Open
pull[bot] wants to merge 1998 commits into
Open
Conversation
Manage this branch in SquashTest this branch here: https://master-n02a3.squash.io |
Only done if `None` is an explicit type, not if `None` is only used as a default value. Fixes #5545.
- Sets require converted values to be Collection instances, being Container is not enough. - We should in general talk about collections, not containers.
- Clarify how true and false strings are handled. - Remove references to ancient RF versions. - Fix indentation with Secret and mention it's new in RF 7.4.
Hopefully makes all tests pass
Logged message can be any `object`, not only `str`, and it is converted to a string automatically.
Plenty of enhancements to BuiltIn: - The absolute biggest change is the added typing (fixes #5544) - Plenty of documentation enhancements - Various enhancements to tests - `timedelta` support to `Repeat Keyword` (fixes #5546) - Few FIXMEs about features to be deprecated - Remove references to RF 4.1 and older
Using `NO VALUES` to disable the `values=False` is deprecated (#5550) and this commit removes such usages. Explict tests need to be still added for validating the deprecation.
Test was broken due to Python's error message being changed.
The value should be omitted altogether or '0' used instead. Part of of #5537.
- Support string normalization (case-insensitivity, stripping and collapsing spaces) also with bytes. This affects all keywords in BuiltIn and Collections that support normalization and accept bytes. - If the first argument to validation keywords in BuiltIn is bytes, convert the second argument to bytes as well. - Enhance documentation related to normalization. - Also enhance documentation related to overriding failure messages. - Some general cleanup. Fixes #5548.
Missing piece of #5548.
Should Be Equal is more powerful these days,
We expect everyone to use Python 3, no need to specify the version.
Also enhance string representation of `Callable` in Libdoc outputs. Fixes #5562.
But it should pass Any and object types Fixes #5520
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Add common base class for built-in loggers. - Rename built-in loggers to use "Console" postfix instead of "Output". - Refactor VerboseConsole so that it has all functionality directly instead of using helper classes. - Refactor highlighting. - Add type hints. - Add docstrings. - ... Main motivation for all this is exposing built-in console loggers so that external console loggers (#5618) can use them.
Part of #5618.
1. Add titles to created links. Markdown already supported titles with reference links and it made sense to use them consistently. 2. Add type references to used type names, not to generic type names. See #5691 for details. Linking to types still needs to be documented. 3. Support references created in introduction also with keywords when using Markdown. 4. Refactor.
We linkify URLs when using other formats and I'm fairly certain users generally expect that also with Markdown. Python-Markdown doesn't support that natively, so needed to create an extension. Part of Libdoc's Markdown support (#5304), but will come if/when we add Markdown support also to suite and test docs (#2549).
For example, use `"Example Keyword" keyword` instead of harder to understand `Example Keyword keyword`.
Only include two highest levels. Part of #5304.
This is part of Libdoc's Markdown support (#5304). Still need to document how to actually use Markdown with Libdoc and what extra features (mostly automatic link targets) it provides. Also some changes elsewhere in the User Guide, mostly to avoid conflicting section headers.
Bumps [actions/checkout](https://github.com/actions/checkout) from 6 to 7. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v6...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 6.2.0 to 6.3.0. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v6.2.0...v6.3.0) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: 6.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Implements (and tests) the parser component of #5604. Still needs to be integrated with rest of the code..
1. Fix bug in handling section indentation. 2. Refactor code so that sections and arguments are represented by a Block class. That moved all indentation handling to same place and reduced duplication also otherwise. 3. Add some docstrings and comments.
It accidentally `str` in some places and `Path` in others. Due to this inconsistency, keyword source was written to XML specs also when it was same as library source. Now source is consistently `str` everywhere.
To discover unit test and run them from VSCode
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
13 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )