mirror of
https://github.com/privatevoid-net/nix-super.git
synced 2024-09-21 08:58:04 +03:00
68c81c7375
I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```
45 lines
2.2 KiB
C++
45 lines
2.2 KiB
C++
#pragma once
|
|
///@file
|
|
|
|
#include <string>
|
|
#include <regex>
|
|
|
|
namespace nix {
|
|
|
|
// URI stuff.
|
|
const static std::string pctEncoded = "(?:%[0-9a-fA-F][0-9a-fA-F])";
|
|
const static std::string schemeRegex = "(?:[a-z][a-z0-9+.-]*)";
|
|
const static std::string ipv6AddressSegmentRegex = "[0-9a-fA-F:]+(?:%\\w+)?";
|
|
const static std::string ipv6AddressRegex = "(?:\\[" + ipv6AddressSegmentRegex + "\\]|" + ipv6AddressSegmentRegex + ")";
|
|
const static std::string unreservedRegex = "(?:[a-zA-Z0-9-._~])";
|
|
const static std::string subdelimsRegex = "(?:[!$&'\"()*+,;=])";
|
|
const static std::string hostnameRegex = "(?:(?:" + unreservedRegex + "|" + pctEncoded + "|" + subdelimsRegex + ")*)";
|
|
const static std::string hostRegex = "(?:" + ipv6AddressRegex + "|" + hostnameRegex + ")";
|
|
const static std::string userRegex = "(?:(?:" + unreservedRegex + "|" + pctEncoded + "|" + subdelimsRegex + "|:)*)";
|
|
const static std::string authorityRegex = "(?:" + userRegex + "@)?" + hostRegex + "(?::[0-9]+)?";
|
|
const static std::string pcharRegex = "(?:" + unreservedRegex + "|" + pctEncoded + "|" + subdelimsRegex + "|[:@])";
|
|
const static std::string queryRegex = "(?:" + pcharRegex + "|[/? \"])*";
|
|
const static std::string segmentRegex = "(?:" + pcharRegex + "*)";
|
|
const static std::string absPathRegex = "(?:(?:/" + segmentRegex + ")*/?)";
|
|
const static std::string pathRegex = "(?:" + segmentRegex + "(?:/" + segmentRegex + ")*/?)";
|
|
|
|
/// A Git ref (i.e. branch or tag name).
|
|
/// \todo check that this is correct.
|
|
const static std::string refRegexS = "[a-zA-Z0-9@][a-zA-Z0-9_.\\/@-]*";
|
|
extern std::regex refRegex;
|
|
|
|
/// Instead of defining what a good Git Ref is, we define what a bad Git Ref is
|
|
/// This is because of the definition of a ref in refs.c in https://github.com/git/git
|
|
/// See tests/functional/fetchGitRefs.sh for the full definition
|
|
const static std::string badGitRefRegexS = "//|^[./]|/\\.|\\.\\.|[[:cntrl:][:space:]:?^~\[]|\\\\|\\*|\\.lock$|\\.lock/|@\\{|[/.]$|^@$|^$";
|
|
extern std::regex badGitRefRegex;
|
|
|
|
/// A Git revision (a SHA-1 commit hash).
|
|
const static std::string revRegexS = "[0-9a-fA-F]{40}";
|
|
extern std::regex revRegex;
|
|
|
|
/// A ref or revision, or a ref followed by a revision.
|
|
const static std::string refAndOrRevRegex = "(?:(" + revRegexS + ")|(?:(" + refRegexS + ")(?:/(" + revRegexS + "))?))";
|
|
|
|
}
|