Rebase against upstream #21
Draft
Conversation
This file contains 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
…yword Signed-off-by: Florian Wühr <[email protected]>
Load a string to a python file as module - PR 1/3
limit keyword split to first match, allow colons to be part of the keyword
Bumps [black](https://github.com/psf/black) from 23.12.1 to 24.3.0. - [Release notes](https://github.com/psf/black/releases) - [Changelog](https://github.com/psf/black/blob/main/CHANGES.md) - [Commits](psf/black@23.12.1...24.3.0) --- updated-dependencies: - dependency-name: black dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
…black-24.3.0 Bump black from 23.12.1 to 24.3.0
Due to the insertion of an new example using the new functionality it was required to update the publish tests which rely on these examples.
Generate sha for files in reference
Remove extra whitespace
Drop support for Python 3.8
Build system was changed in ddbe061 to use poetry-core, but pyproject.toml still depends on the whole poetry
Update build-system requirement to poetry-core
Fix runner version to macos-13, as setup-python only support >=3.11 on osx 14
Ignore minimised JS when grepping
extended the original `.doorstop.yml` config file to read a custom item validator per folder. Using this new validator extended door document and item behaviour to check the checksum for each reference and if they changed during the validate step from doorstop.
a few things later
The function will be reused to load an external doorstop config file through command line
It was added when option to define a settings.py file which will override only valid options. Fix comment regarding why we don't with an exception
Including an option to render referenced AsciiDoc files as part of document output
Updated pyproject to deal with setuptools removal in 3.12 and tagged the version with a codethink tag to cover work that is not part of the original repo
We are planning to rely on git tags and GitHub releases to maintain the code for doorstop. This PR proposed that when we do a tag, an automatic pipeline generates a release. The current workflow for a release is: 1. A tag must pass the same tests from a PR before a release. 2. It needs to be able to at least be build in 3.10, 3.11 and 3.12.
Now at least we can see the results properly in CI.
Now it uses builtins.Exception instead of Exception
- We now are using yield from instead of yielding a value, - There is a debate about onerror deprecation parameter for `shutil.rmtree`, which I'm not entirely sure what would be the outcome, but this is not something that we should be concerned about, at least for now. So warning W4903 is going to be ignored, as we still need to use `onerror` parameter to support python 3.10 and 3.11 - Inserted a placeholder for invalid editor. - Error `E0606` is going to be ignored for now, as there is no way to use document without it beem defined earlier, but unfortunately the linter is not capable of identify it.
Doorstop already has a setting to run custom configuration with the flag --setings, as a second option now doorstop can read a file named '.doorstoprc.py' to override the default settings
Adds a new settings item to control the markdown output by the publish command, making it suitable for rendering using mkdocs (specifically mkdocs-material). Signed-off-by: Paul Albertella <[email protected]>
If we run doorstop with debug and we are overriding the defaults we are going to see it.
Missed this line when updating the CI setup
Doorstop excludes hidden files from paths included in its representation of the version control system files, but this means that e.g. CI config files in a hidden folder cannot be included in the references of an item. This patch allows users to specify file patterns that should not be hidden in a file (default name: .doorstop_unhidden)
Includes 0.1 updates to change log
Make markdown files POSIX compliant by ensuring the final line always has a trailing newline.
We added an implementation that pull a remote parent for a doorstop document if not present. It also validates if you try to import a prefix twice with different tags and also does recursive download if required. You need to change your `.doorstop.yml` to add the following ``` external_parent: <git repo url (with .git)> external_parent_tag: <tag> settings: parent: <PARENT PREFIX> ````
Added how to use it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.