Skip to content
This repository was archived by the owner on Dec 23, 2021. It is now read-only.

Nice form to use#18

Merged
bdero merged 1 commit intomasterfrom
feature/user_interface
Mar 27, 2015
Merged

Nice form to use#18
bdero merged 1 commit intomasterfrom
feature/user_interface

Conversation

@carsongee
Copy link
Copy Markdown
Contributor

This adds a form to exercise the edx-platform form. It has a dependency on #11, so that is why it looks extra huge. Once that merges, this should be a bit easier to test:

Start form

image

Successful

image

Failed

image

@carsongee carsongee force-pushed the feature/user_interface branch 2 times, most recently from a5c4444 to a393674 Compare March 20, 2015 22:27
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+8.31%) to 97.0% when pulling a3936746d02a1a7e0495814c6045b478a9aec439 on feature/user_interface into f7aba5d on master.

@carsongee carsongee force-pushed the feature/user_interface branch 2 times, most recently from 4572447 to b849e09 Compare March 25, 2015 21:17
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.37%) to 97.0% when pulling b849e09eee5cbf70a373b946c4f35d15ff0eac66 on feature/user_interface into 0c70bf1 on master.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.37%) to 97.0% when pulling b849e09eee5cbf70a373b946c4f35d15ff0eac66 on feature/user_interface into 0c70bf1 on master.

@carsongee
Copy link
Copy Markdown
Contributor Author

Rebased and ready for review

@pwilkins
Copy link
Copy Markdown
Contributor

When I click the get sections button I get this error report. Apart from getting the error, the error report message scrolls off the right margin and clicking the Traceback button displays white text on a light grey background.
lmod_proxy_get-sections_error

@carsongee
Copy link
Copy Markdown
Contributor Author

Here is the relevant github issue for the underlying bug in pylmod: mitodl/PyLmod#30. As discussed the unfortunately ugly error message is due to having flask in debug mode. If you want to try it with DEBUG=False in the settings (i.e. through uwsgi or gunicorn) and it is still a mess I could definitely fix it up.

@carsongee
Copy link
Copy Markdown
Contributor Author

As another comment to @pdpinch suggestion to remove get-sections, I'm not sure I really want to do that with some more thought. I don't know who/what else maybe consuming that API feature since we are basically black box redesigning grades2stellar. So I think we probably want to leave it in there and fix pylmod.

@pdpinch
Copy link
Copy Markdown
Member

pdpinch commented Mar 26, 2015

Fair point. Does mitodl/PyLmod#30 block this merge? Does it block a release of lmod_proxy?

IMO, no on 1, assuming we add an issue to track it. Yes on 2, for the same reason you outline @carsongee

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Any need for these console.logs? It seems that the convenience of network tools in modern browsers should eliminate the need.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I was logging them for introspection of the object I was getting back (which wasn't what I thought it was at first), not for the actual data coming back. I'll remove them since they are now the expected object and you are correct on the network tools

@bdero
Copy link
Copy Markdown
Contributor

bdero commented Mar 26, 2015

Looks 🏆 after taking a look at my few minor suggestions.

@Ferdi
Copy link
Copy Markdown

Ferdi commented Mar 26, 2015

Just curious, why do we need an actual form ? Who is going to use it ?

@bdero
Copy link
Copy Markdown
Contributor

bdero commented Mar 26, 2015

It's a convenient way of testing the LMOD gradebook API; developers will use it.

@carsongee
Copy link
Copy Markdown
Contributor Author

@pdpinch this bug has already been in here since #11 landed, so the issue while identified here isn't caused by this PR. Because of that, I wouldn't think it should block the merge.

@carsongee
Copy link
Copy Markdown
Contributor Author

I read your comment more thoroughly @pdpinch and realized I didn't answer the second piece. Yes, I think this blocks both a release of pylmod and lmod_proxy since we would want this resolved before switching to these in production

@carsongee carsongee force-pushed the feature/user_interface branch from b849e09 to 494975a Compare March 26, 2015 20:17
@carsongee
Copy link
Copy Markdown
Contributor Author

@bdero the '' part of .join('') is very important and hard to debug lol. I think I've addressed your comments.

@carsongee carsongee force-pushed the feature/user_interface branch from 494975a to fefe069 Compare March 26, 2015 20:19
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.37%) to 97.0% when pulling 494975ab33bd089dff9f762e4d7179ae1e95d41a on feature/user_interface into 0c70bf1 on master.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.37%) to 97.0% when pulling fefe069 on feature/user_interface into 0c70bf1 on master.

@bdero
Copy link
Copy Markdown
Contributor

bdero commented Mar 27, 2015

Sorry about forgetting to include the '' for the join(). I think all is well now, so merging.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants