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

[Init] Initial works to split the json schema widget into a package. #1

Merged
merged 27 commits into from Mar 3, 2019
Merged

Conversation

auvipy
Copy link
Collaborator

@auvipy auvipy commented Apr 16, 2018

No description provided.

Copy link
Collaborator Author

@auvipy auvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

travis config, tests and some clean up needed probably.

@@ -0,0 +1,117 @@
a.button:focus,
a.jsoneditor-exit:focus{ text-decoration: none }
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be this should be dropped

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this code is imported from the current implementation we can leave it as is, we can deal with the UI in the next step

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i agree

@auvipy
Copy link
Collaborator Author

auvipy commented May 23, 2018

@nemesisdesign could you check if this is nearby for initial merge and manual testing? some minor tweaks may be needed, I will start work on test after this is in

CONTRIBUTING.rst Outdated Show resolved Hide resolved
docs/installation.rst Outdated Show resolved Hide resolved
Copy link
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great progress @auvipy 👍 see my comments

@@ -0,0 +1,117 @@
a.button:focus,
a.jsoneditor-exit:focus{ text-decoration: none }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this code is imported from the current implementation we can leave it as is, we can deal with the UI in the next step

docs/installation.rst Outdated Show resolved Hide resolved
docs/index.rst Show resolved Hide resolved
AUTHORS.rst Outdated Show resolved Hide resolved
CONTRIBUTING.rst Outdated Show resolved Hide resolved
docs/usage.rst Outdated Show resolved Hide resolved
setup.py Outdated Show resolved Hide resolved
tests/settings.py Show resolved Hide resolved
@auvipy
Copy link
Collaborator Author

auvipy commented Aug 28, 2018

probably I have addressed the comments. except for sphinx. do you think this pr is ok to get in?

Copy link
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@auvipy ready for manual testing, I will test as soon as possible and added this to my TODO list.

I left some comments regarding minor improvements.

AUTHORS.rst Outdated Show resolved Hide resolved
AUTHORS.rst Outdated Show resolved Hide resolved
{% endblock javascript %}

{% endblock extra_js %}
{% endcomment %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get the point of this file

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will take care of this after your manual testing. other comments are addressed hopefully

jsonschema_widget/urls.py Outdated Show resolved Hide resolved
tests/urls.py Outdated Show resolved Hide resolved
@nemesifier nemesifier added this to To do (general) in OpenWISP Contributor's Board via automation Aug 28, 2018
@nemesifier nemesifier moved this from To do (general) to In progress in OpenWISP Contributor's Board Sep 28, 2018
@nemesifier
Copy link
Member

Will get here asap.

@auvipy
Copy link
Collaborator Author

auvipy commented Oct 4, 2018

OK. Looking forward to it

Copy link
Member

@atb00ker atb00ker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested it out openwisp/django-netjsonconfig#96 ; first project to use this repository looks like working ! 👍
Note: I had to make changes for Django-2.1 compatibility: https://github.com/atb00ker/django-jsonschema-widget
I have a couple of questions / comments:

  1. Should we start with automated testing? 😄
    (please read more questions below)

setup.py Outdated Show resolved Hide resolved
manage.py Outdated Show resolved Hide resolved
requirements.txt Show resolved Hide resolved
</label>
"""
html = html.format(_('Advanced mode (raw JSON)'),
reverse('netjsonconfig:schema'))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Since we are moving it out of netjsonconfig, my assumption is that it's planned to be used at other places as well!
    Hence, shouldn't all these values be either variables (to be set from the settings file) or changed and made generalised to keep any project in mind!
    I am not only talking about the reverse here, but also values above are keeping only that one project in mind!

Please correct me if i've understood it incorrectly! 😄

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I not sure right now, @nemesisdesign might have better insight than me in this regard.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@atb00ker is right, here I explain our main use cases: #2
I think we can work on this in the next iterations, for the moment let's focus on making it work properly on django-netjsonconfig, even if it's dirty (we won't release it yet).

@auvipy
Copy link
Collaborator Author

auvipy commented Nov 1, 2018

added Django 2.1 related changes. will start working on automated testing after this get merged initially. for automated test, which approach or tools you prefer?

Copy link
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found Issues during manual testing on django-netjsonconfig and reported to openwisp/django-netjsonconfig#96 (review)

I propose the following: let's fix the easiest stuff (namings and conventions) and leave the harder stuff for more iterations, let's merge, I'm adding both of you to have write permissions to the repo so we can work on it together here.

We can also create some GCI tasks for improvements like using Pipenv and similar, while we focus on making the package work and get it to the point that we can issue the first release and we can merge openwisp/django-netjsonconfig#96

setup.py Outdated Show resolved Hide resolved
tests/settings.py Outdated Show resolved Hide resolved
manage.py Outdated Show resolved Hide resolved
requirements.txt Show resolved Hide resolved
requirements_test.txt Outdated Show resolved Hide resolved
requirements_dev.txt Outdated Show resolved Hide resolved
setup.cfg Show resolved Hide resolved
@auvipy
Copy link
Collaborator Author

auvipy commented Nov 7, 2018

thanks for your review, Will fix the easier tasks first and after that will merge and start more iteration for the next concerns.

@nemesifier
Copy link
Member

Great, thanks. I enabled also travis and coveralls

@auvipy auvipy self-assigned this Nov 7, 2018
@atb00ker
Copy link
Member

P.S: Also, the commit guidelines of the rest of the projects for consistency! 😊

@auvipy
Copy link
Collaborator Author

auvipy commented Nov 21, 2018

should I disable jslint check for now? or fix them all?

Copy link
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@auvipy
Copy link
Collaborator Author

auvipy commented Nov 22, 2018

OK

@auvipy
Copy link
Collaborator Author

auvipy commented Dec 9, 2018

what's the reason for build failures? any hints for fixing it?

@auvipy
Copy link
Collaborator Author

auvipy commented Dec 9, 2018

I want to get this in and start working on automated testing

Copy link
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@auvipy thank you for pinging us, we've been super busy with the Google Code-In which is almost over now.

I left you some comments that should help you resolve the situation. Once you have done please squash the commits into one.

.travis.yml Outdated Show resolved Hide resolved
requirements-test.txt Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
django_jsonschema_widget/models.py Outdated Show resolved Hide resolved
.travis.yml Outdated

script:
- coverage run --source= runtests.py
- if [[ $TRAVIS_PYTHON_VERSION == 3.4 ]]; then ./tests/manage.py makemigrations --dry-run | grep "No changes detected"; fi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can also remove the migration check because we don't have any model

@auvipy
Copy link
Collaborator Author

auvipy commented Dec 10, 2018

I will address all the issues tomorrow.

@auvipy
Copy link
Collaborator Author

auvipy commented Dec 12, 2018

I might have messed up something in shell section, could any of you take another look? do we need to add django as a dependency on requirements-test?

Copy link
Member

@nemesifier nemesifier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@auvipy is just the commit message style check doing its job, we added a check in all our modules to ensure the commit message style used is consistent so that the commit log of each project is readable

Could you please clean up the commit history of this PR so we can merge?

The fastest way is to squash all the previous commits into one and give it a message like:

[init] First commit

@auvipy
Copy link
Collaborator Author

auvipy commented Mar 2, 2019

I must have to do this before this week ends!!!

@atb00ker
Copy link
Member

atb00ker commented Mar 2, 2019

Great, thanks! 👍

@auvipy auvipy changed the title WIP - Do not merge [Init] Initial works for splitting the json schema widget Mar 2, 2019
@auvipy auvipy changed the title [Init] Initial works for splitting the json schema widget [Init] Initial works to split the json schema widget into a package. Mar 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants