Description
Classify a Cargo profile and supplied inheritance parent.
Package and container references combine names, selectors, conditions and platform metadata. A restricted lexical split can preserve these parts without validating registry identity, available targets, dependency graphs or runtime resolution.
Classify a Cargo profile and supplied inheritance parent.
When to use this tool
Use Cargo Profile Inheritance Key when checking the stated package, Cargo or container-reference component.
How to use the tool and how it works
- Enter profile, inherits. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read customProfile, inheritanceRequired, builtInParent. Inspect customProfile, inheritanceRequired, builtInParent before interpreting the associated values.
Classify a Cargo profile and supplied inheritance parent. Require nonempty profile/inherits; profiles outside dev/release/test/bench are custom and require inheritance; builtInParent recognizes only dev or release.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| profile | Profile | Required. Text; maximum UTF-16 length 8192. |
| inherits | Inherits | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| customProfile | Custom Profile | Required. Boolean. |
| inheritanceRequired | Inheritance Required | Required. Boolean. |
| builtInParent | Built In Parent | Required. Boolean. |
{
"input": {
"profile": "production",
"inherits": "release"
},
"output": {
"customProfile": true,
"inheritanceRequired": true,
"builtInParent": true
}
}Limitations and assumptions
- This does not validate the full profile table, inheritance cycles or actual Cargo behavior.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the relevant package manager, runtime or registry against the actual project for complete resolution and validation.
References
Similar or alternative tools
- Cargo Feature Dependency Prefix Token
Parse one restricted Cargo dependency-feature token.
- Cargo Dependency Rename Package Pair
Compare local and package names in a Cargo rename record.