-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use XSpec variable instead of entity #1136
Merged
Merged
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
david-waltermire
force-pushed
the
develop
branch
from
February 26, 2022 20:10
8b6ebe6
to
71cb482
Compare
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
david-waltermire
force-pushed
the
wip-textent-to-xvar
branch
from
February 28, 2022 14:12
42e56cf
to
c732475
Compare
wendellpiez
approved these changes
Feb 28, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! (I have much to learn. Please continue.)
david-waltermire
approved these changes
Feb 28, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
david-waltermire
pushed a commit
that referenced
this pull request
May 17, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
david-waltermire
pushed a commit
that referenced
this pull request
Jun 21, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
david-waltermire
pushed a commit
that referenced
this pull request
Jul 13, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
david-waltermire
pushed a commit
that referenced
this pull request
Aug 23, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
to aj-stein-nist/OSCAL-forked
that referenced
this pull request
Oct 6, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
that referenced
this pull request
Oct 18, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
david-waltermire
pushed a commit
that referenced
this pull request
Oct 31, 2022
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
to aj-stein-nist/OSCAL-forked
that referenced
this pull request
Jan 10, 2023
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
to aj-stein-nist/OSCAL-forked
that referenced
this pull request
Feb 6, 2023
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
to aj-stein-nist/OSCAL-forked
that referenced
this pull request
Jun 29, 2023
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
to aj-stein-nist/OSCAL-forked
that referenced
this pull request
Jul 10, 2023
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
aj-stein-nist
pushed a commit
to galtm/OSCAL
that referenced
this pull request
Sep 28, 2023
For consistency with select.xspec, use XSpec variable instead of entity for the path to the profile resolution examples.
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.
Minor follow-up to #1101: For consistency with select.xspec, make select-rlink.xspec use an XSpec variable instead of an entity,
for the path to the profile resolution examples.
I qualified this change by running the test in Oxygen.
All Submissions:
Changes to Core Features:[ ] Have you added an explanation of what your changes do and why you'd like us to include them?[ ] Have you written new tests for your core changes, as applicable?[ ] Have you included examples of how to use your new feature(s)?[ ] Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.