-
Notifications
You must be signed in to change notification settings - Fork 177
Why is this git so unresponsive? #263
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
Comments
@dschnelldavis Are you still maintaining this repo? There is a growing list of users who are actively adding issues/PR's but not seeing any movement on them. If your no longer maintaining this, can we see about transfering ownserhip? Maybe see if the @json-schema-form group is interested in taking it? |
My guess is that @dschnelldavis is busy with the newer, ng6-compatible version of this repo, over at |
Thast's just someone else's fork, not a newer version. I believe @shamoons is going to try and move forward with his fork here https://github.com/shamoons/ng-json-schema-form |
@jscharett that's correct. I'm going to move forward with it at https://github.com/shamoons/ng-json-schema-form I'm in the process of reviewing existing PR's currently. |
@RichardMViGEM Nice try. That repo is a fork, @dschnelldavis has no involvement with
I am offering to contribute to @shamoons's repo, glad he has more time to dedicate to this library. |
@shamoons After installing your package via npm (npm install ng-json-schema-form) there are alot of error when you load the module. |
Not sure if this is the issue, but your using Angular 6. I don't think @shamoons fork has been updated to support Angular 6 yet. |
@shamoons Looking at the deployed package that's coming down for ng-json-schema-form, it looks like it may not be compiled correctly? Its def different than the deployed package for this repo. Any reason for that? |
I'll take a look this weekend |
I enabled issues on https://github.com/shamoons/ng-json-schema-form |
I'm posting many issues but the contributors hardly reply. Disappointed with such a nice git.
The text was updated successfully, but these errors were encountered: