Allow absolute OCCweb path - #369
Merged
Merged
Conversation
51 of 55 tasks
jeanconn
approved these changes
Jan 7, 2026
This was referenced Jan 14, 2026
Merged
Merged
This file contains hidden or 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
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.
Description
This is a small change to make the
occweb.get_occweb_*functions a bit more tolerant. The current expectation is that the user provides a relative path likeFOT/mission_planningwhich is then joined to the default OCCweb URL root. The problem is that providing the path as/FOT/mission_planningseems innocuous (based on the documentation) but will cause the current code to fail.Interface impacts
An absolute OCCweb path will now work more intuitively to give the expected result.
Testing
Unit tests
Independent check of unit tests by Jean
Functional tests
No functional testing.