Skip to content

Conversation

@janwirth
Copy link

No description provided.

@klazuka
Copy link
Owner

klazuka commented Nov 26, 2019

Thanks, but I want to keep this package focused on the UI part.

In my main Elm project where I extracted this from, we do use keypaths more heavily, but I want to avoid going in that direction in this package.

@klazuka klazuka closed this Nov 26, 2019
@janwirth
Copy link
Author

I must say this rejection forces me to maintain a fork as my project also heavily relies on keypaths. I think this package has potential beyond demo apps if we make the keypaths more expressive.

@klazuka
Copy link
Owner

klazuka commented Nov 27, 2019

@FranzSkuffka I know. My other app uses the keypaths to do type-safe lookup in the JSON. I never open-sourced that part because it seemed like too much of an edge case. But I guess if there are other people with similar needs, maybe I should go ahead and bring it in.

What kind of stuff are you using the keypaths for?

@klazuka klazuka reopened this Nov 27, 2019
@janwirth janwirth changed the title GH-5 - Make KeyPath more expressive WIP - GH-5 - Make KeyPath more expressive Nov 28, 2019
@janwirth
Copy link
Author

I am developing a tool that allows you to easily focus on a subset of information of a data source like an API in order to expose it for further use (this includes type-safe parsing).

Just pushed a new commit transferring changes from my one-file-fork in the private project.

@janwirth janwirth changed the title WIP - GH-5 - Make KeyPath more expressive GH-5 - Make KeyPath more expressive Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants