Skip to content

Feature Request: Consider empty string IDs null #49

@Earthmark

Description

@Earthmark

In rust having a null string requires a few additional layers that negatively impact library useability.

Currently I have a layer that omits empty strings to keep the useability, but I'm realizing I'm not sure there's a good use case for empty string IDs anyways. I imagine other languages may have similar behaviors, it might make sense to just support that in the library itself.

Would it be possible to have ResoLink consider empty strings the same as null? I don't see much of a use case for an empty string ID aside from this particular case of a null sentinel in practice anyways.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions