-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: rewrite of the Ember frontend #143
Conversation
7912826
to
cbfe2f8
Compare
As discussed this my attempt to overcome the burdens of a legacy application that resisted my attempts to update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So there are a few things which are issues concerning more than one file (as always open for discussion):
- Format
.hbs
with prettier - Notify user if you redirect them out of permissions checks for less confusion
- Please re add acceptance tests since it seems like you completely remove d mirage and all acceptance tests
- Do you not need the
public/assets
anymore?
Currently, the project only uses UIkit assets. This will probably change with the design for the login page. Acceptance tests are something I cannot argue against. Most/all other tests can - IMO - be done through unit and integration tests. But I will port Mirage and the acceptance tests from the old version 😃 |
Some proxies remain (for now).
It looks like I'm not a project admin on Travis. If you are neither I'll ask around. |
This will provide preset-env out of the box.
This adds the block-indentation rule to the template-lint config and adjusts the tempaltes accordingly.
* Sets a more neutral description. * Corrects legacy email address. * Adds another maintainer.
Tell the user that he doesn't have access before redirecting.
Where not necessary.
As the query param is accessible through the transition.
Performance integration leads to an error.
I forgot to remove the timed prefixes in the tests.
🎉 |
Depends on #142
As discussed this my attempt to overcome the burdens of a legacy
application that resisted my attempts to update.