-
-
Notifications
You must be signed in to change notification settings - Fork 155
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 non-primitive values #171
Conversation
Signed-off-by: Richie Bendall <[email protected]>
It should be implemented in |
What about |
Also see, sindresorhus/conf#89. I'm not entirely happy with that way either. |
From a quick glance, it has a lot of issues. I think ideally, we would only use |
But since we need to store it in a meta-field anyway, we could use a nicer human-friendly representation. Which brings us back to sindresorhus/conf#89. |
Perhaps the serialiser can decide on what the meta-field should be called to avoid limitations on naming and serialise with The deserialiser can then look at the JSON and given the same set of rules the serialiser used, discover the name of the meta-field and reverse what it did. |
Not sure I understand what you mean. The meta-field name would be hard-coded. It would contain the same structure as the top-level ones. See the discussion in sindresorhus/conf#89. |
Payment |
New plan: Make the |
Continued in sindresorhus/conf#154 |
Since this method replaces the normal serialization in order to work, we might want to store this behind an option instead. It might also make sense to move this to conf instead.
Fixes: #18
IssueHunt Summary