Skip to content
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

missing make_from_separate #19

Open
phgachoud opened this issue Feb 26, 2020 · 2 comments
Open

missing make_from_separate #19

phgachoud opened this issue Feb 26, 2020 · 2 comments

Comments

@phgachoud
Copy link
Contributor

phgachoud commented Feb 26, 2020

Don't know the politic of this lib about changing some things and if worth it making a pull request about that but, I would have needed a make_from_separate feature. As I already made a pull request and did never have any answer about it I don't want to spend more time trying to contribute to it if it doesn't worth it.

What option should I take

  1. implement it and do a pull request
  2. what I'm doing actually which is inheriting from it and define that function
@jocelyn
Copy link
Member

jocelyn commented Feb 26, 2020

Indeed we haven't noticed your previous pull request. (note we merged your previous PR today... very long delay).

So please, fill a Pull request for this make_from_separate topic, and we'll review and hopefully merge it.

If you don't get comment on GitHub within 48 hours, please contact me directly as you recently did.

@phgachoud
Copy link
Contributor Author

Starting on my fork on branch readme_scoop_functionalities on https://github.com/phgachoud/json/blob/readme_scoop_functionalities/library/kernel/json_array.e The idea is to provide a make_from_separate as the topic of this issue. What do you think about the topic and best practices. The point is that the make_from_separate (other: separate like Current) has to call a fill procedure, this one has to create non separate objects from existing separate objects which are descendants of JSON_VALUE, and all of them. I don't see any other way then what I implemented which I already shared into the google groups which is creating (depending on a type check) non separate JSON_OBJECT, JSON_STRING, etc and then extend the current container. Do you see any much more generic option for that?

I'll commit my proposition as soon as I get it.

Thx in advance

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

No branches or pull requests

2 participants