Skip to content
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

Change label for spatial_local also! #37

Merged
merged 3 commits into from
Jul 2, 2024
Merged

Change label for spatial_local also! #37

merged 3 commits into from
Jul 2, 2024

Conversation

mlhale7
Copy link
Contributor

@mlhale7 mlhale7 commented Jul 2, 2024

What does this PR do?

This also changes the label for our spatial_local property (in addition to spatial). Since we have geographic values without URIs, we have two properties for the same content (differentiated by their form - string or URI). I neglected to address this earlier. Throughout our M3 we are using the same label for the controlled and uncontrolled values (except for with the keyword and subject properties).

How should this be tested?

Did I leave anything else out? Do all the checks for formatting pass?

Copy link
Member

@mkaljns mkaljns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I didn't know about this one.

@mlhale7
Copy link
Contributor Author

mlhale7 commented Jul 2, 2024

I'm going to iterate this up to v40.5 so that production will recognize this as a new/changed profile.

@mlhale7
Copy link
Contributor Author

mlhale7 commented Jul 2, 2024

Sadly we have to go up by 1 apparently for production. I'll make a final change (apologies as I learn how to work with the system).

@mlhale7 mlhale7 merged commit aa45734 into main Jul 2, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants