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

Support a Metadata's option to load/save unsafe YAML types #612

Open
roll opened this issue Jan 7, 2021 · 0 comments
Open

Support a Metadata's option to load/save unsafe YAML types #612

roll opened this issue Jan 7, 2021 · 0 comments
Labels
feature New functionality

Comments

@roll
Copy link
Member

roll commented Jan 7, 2021

Overview

See the original issue - #608

The same as we have done with metadata.to_json(...encoder_class) we can give users an ability to store non-primitive types in YAML descriptors. It's not interoperable but can be useful within some projects e.g. working with numpy.

By default, I think we should load only safe types. The logic is similar to Package/Resource(trusted=True) when the user can allow unsafe paths.


Actually, I guess we can re-use this trusted flag, pass it to Metadata and allow unsafe types loading alongside unsafe paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality
Projects
Status: No status
Development

No branches or pull requests

1 participant