Skip to content

[18.0][IMP] fs_folder: Don't raise an error when the value is invalid or un…#635

Draft
lmignon wants to merge 2 commits into
OCA:18.0from
acsone:fs_folder_invalid_value
Draft

[18.0][IMP] fs_folder: Don't raise an error when the value is invalid or un…#635
lmignon wants to merge 2 commits into
OCA:18.0from
acsone:fs_folder_invalid_value

Conversation

@lmignon

@lmignon lmignon commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

…available

When the value of a fs_folder field is invalid or unavailable, it will now return a FsFolderInvalidValue or FsFolderUnavailableValue object instead of raising an error. This allows for more graceful handling of these cases in the code and more importantly, it will no longer break the form view when the value is invalid or unavailable.

…available

When the value of a fs_folder field is invalid or unavailable, it will now
return a FsFolderInvalidValue or FsFolderUnavailableValue object instead
of raising an error. This allows for more graceful handling of these cases
in the code and more importantly, it will no longer break the form view
when the value is invalid or unavailable.
@lmignon

lmignon commented Jun 29, 2026

Copy link
Copy Markdown
Contributor Author

ping @xavier-bouquiaux

@lmignon lmignon marked this pull request as draft June 29, 2026 15:17
when reading the object the js was not aware of this new isInvalid or is Unavailable -> add it to the if
the wrong method was called in the xml, trying to physically remove the folder that we know does not exists on the fs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants