Allow saving Type objects to TypeInfo.metadata
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
They are already being saved to cache and have serializer/deserialize methods.
It could also be generalized by creating smth like Serializable interface
class Serializable:
serialize
@classmethod
deserialize
and require all cache serializable objects to implement it to be able to be saved to cache.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing TypeInfo.metadata and the existing cache serialization path described in the issue. Review how Type objects already use serializer/deserialize, then determine how metadata persistence should support them and whether a shared Serializable interface is needed. Done means Type objects can be saved to and restored from TypeInfo.metadata without breaking existing cache behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100