-
Notifications
You must be signed in to change notification settings - Fork 76
Metadata can appear to be set directly, but doesn't work: unfriendly to the user #993
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
Comments
Thoughts @benjeffery? |
Tough one this as supporting the assignment (recursively) is not that simple, possible though I assume. We could return a frozendict, but would need a nice error message. I'll look into supporting the assignment, if it gets too hairy (for example should `del tc.metadata['foo']['bar'] work?) I'll try freezing. |
I'd say a frozendict would be a good first step - actual assigmnent will be hairy and would need some more low-level infrastructure for setting values in rows. |
Ah, yes. I'd only considered the ts-level case. |
Making it read-only would be fine, IMO. |
FWIW here's a situation where (I'm not sure but I suspect) things were hard to figure out for a user because it seems like you can just change metadata but it doesn't do anything: https://groups.google.com/g/slim-discuss/c/N2v0fyiYOoQ/m/pHZ9h5v0CAAJ A natural thing for this user to try would have been
but those just silently do nothing. |
Retuning a frozendict is an easy thing to do for 1.0 I think @benjeffery ? |
I see that it looks like I can set metadata properties after creating them, but it doesn't actually update the metadata. I think it should either work, or we should raise an error if possible:
The text was updated successfully, but these errors were encountered: