Feature: mappable meta#12
Merged
Merged
Conversation
Contributor
|
@vadymmarkov what about the README? 😁 |
Contributor
|
My wonder is about this |
Contributor
Author
|
This is interesting idea @onmyway133. What do you think @zenangst? It could be some additional protocol, so you should have title, subtitle, kind and so on on your struct. But it's Mappable at the same time. |
Contributor
|
I like this idea! 😁 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

@zenangst
Got a new idea regarding our discussions about meta. So instead of using enums or magic generators we can use Mappable structs 😄
My only concern is than it might be too much code, because you have to implement mapping, don't see any way to avoid this, even though property key always reflects the property name. But with this approach you write string only once which is nice.