Skip to content

104 raise errors when appropriate in is public method#105

Merged
BMatischen01 merged 8 commits into
developmentfrom
104-raise-errors-when-appropriate-in-is_public-method
Sep 3, 2025
Merged

104 raise errors when appropriate in is public method#105
BMatischen01 merged 8 commits into
developmentfrom
104-raise-errors-when-appropriate-in-is_public-method

Conversation

@BMatischen01

@BMatischen01 BMatischen01 commented Sep 3, 2025

Copy link
Copy Markdown
Collaborator

Closes #104 by adding explicit code checks in is_public for 401 and 403, which are valid codes to indicate a project is not public. Any other codes or expected errors are raised, and regression tests have been added to ensure the errors raised from is_public get caught when it's used in cli.py and exporter.py.

@douglowe douglowe left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

couple of small changes, otherwise looks reasonable

Comment thread src/osfexport/exporter.py
Comment thread tests/test_clitool.py Outdated
@BMatischen01
BMatischen01 merged commit 0bebd6d into development Sep 3, 2025
1 check passed
@SJaffa
SJaffa deleted the 104-raise-errors-when-appropriate-in-is_public-method branch September 4, 2025 14:30
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