[pull] master from robotframework:master - #145
Open
pull[bot] wants to merge 2130 commits into
Open
Conversation
Manage this branch in SquashTest this branch here: https://master-n02a3.squash.io |
Remove the separte Hybrid library API section and instead document how to control keyword discovery using `get_keyword_names` under the Creating keywords section. The section about controlling keyword discovery was pretty messy and it was restructured as part of this change. The first part of #5634.
Move the section about the dynamic library API from the Creating test libraries section so that it is directly under the Extending Robot Framework chapter. Fixes #5634.
Bumps the npm_and_yarn group with 1 update in the /src/web directory: [picomatch](https://github.com/micromatch/picomatch). Updates `picomatch` from 2.3.1 to 2.3.2 - [Release notes](https://github.com/micromatch/picomatch/releases) - [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md) - [Commits](micromatch/picomatch@2.3.1...2.3.2) --- updated-dependencies: - dependency-name: picomatch dependency-version: 2.3.2 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
npm: bump handlebars dependency to 4.7.9
…src/web/npm_and_yarn-66413a1f6e Bump picomatch from 2.3.1 to 2.3.2 in /src/web in the npm_and_yarn group across 1 directory
Minor documentation change to avoid confusion between WHILE and "while"
- Minor code changes. - Make new unit tests consistent with old ones. - Add some more unit tests.
Use VariableMatch that's anyway needed in different finders to avoid unnecessary decoration and undecoration. Code gets a bit simpler and there ought to be small performance benefits as well. This was done as part of investigating #5644. Some type hinting as well.
Most importantly, avoid using somewhat expensive `variable_not_found` in cases where the error message it produces would anyway be ignored. Part of #5644.
Decorating only actual recommendations is faster than decorating all candidates because there are lot less variables to decorate. This is related to enhancements for resolving variables (#5644). After earlier changes this code is run only when variables aren't actually found, so performance benefits are only seen in error situations.
The main motivation is having less occurrences of `return cls(...)` to make it easier to change them to `return cls(..., alias=alias)`. That is needed for proper `type` statement support (#5760).
The only usage outside `robottypes` where it was defined was removed in the previous commit and it isn't really needed in `robottypes` either. Better to deprecate it now and remove later. Issue #5639 covers all `robot.utils` deprecations in RF 7.5.
To some extend related to #5709. Also, make doc strings using `\` raw strings to avoid escaping like `\\`.
Related to #5709.
Part of Markdown support (#5304).
These arguments will be renamed to `list` and `time`, respectively, in Robot Framework 8.0. Recommend passing arguments positionally instead of using the named argument syntax. Fixes #5763.
Tests having `List Should Contain Value` in their name when they actually tested `Should Contain Match` was confusing, especially because the library also has keyword `List Should Contain Value` that has its own tests as well.
Report a warning if using full match changes the behavior. Fixes #5765.
`isinstance(Union, type)` is true nowadays but wasn't earlier.
This is the second part of the `type` statement support (#5760). The info still needs to be shown in Libdoc HTML and Markdown outputs.
Use own variables with each example to make them easier to understand and execute locally. Part of #5709. --------- Co-authored-by: Vincent <vincent.verbeek@cbr.nl>
Part of #5709. --------- Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com>
Use local variables instead of global ones except in cases where same
variables are used by multiple related tests. This allows using simple
and short names like `@{list}` and `&{dict}`. Global variables need to
be unique or otherwise examples cannot be easily executed, and that had
required names to be long like `@{ITEM_ASSIGNMENT_1}`.
Part of #5709.
Fixes #5749. Co-authored-by: Tatu Aalto <tatu.aalto@op.fi>
Earlier setup could left code to inconsistent state if linting failed.
Implementation and tests done. TODO: - Change standard library docs using admonitions to use new syntax. - Update documentation. - Update styles. Part of #5304.
Also remove outdated info about differences with Robot format.
Update the User Guide docs and add related API docs. Part of #5304.
Part of #5709. --------- Co-authored-by: Vincent <vincent.verbeek@cbr.nl>
Part of #5709. Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com>
- typo fix (didn't know purplish is a word) - make type checker happy
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
16 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 : )