-
Notifications
You must be signed in to change notification settings - Fork 63
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
Default tab fixed for Library page - issue #3871 #3897
Conversation
When a user clicks on Library they see Blueprints route as default. But it should be Team Library route. That was the problem and by this commit this issue has been solved
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.
/home/runner/work/flowfuse/flowfuse/frontend/src/pages/team/Library/index.vue
42:18 error Unexpected trailing comma comma-dangle
/home/runner/work/flowfuse/flowfuse/frontend/src/pages/team/Library/routes.js
6:77 error Unexpected trailing comma comma-dangle
Please fix the errors/warnings reported in the tests
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.
I have a feeling that some e2e tests will also fail after fixing the lint errors due to the library's default page being changed
Can anyone please give me some hints on how can I solve it? I am new at testing this type of large codebase. Though I haven't read the full codebase yet. On the test result/error, it is indicating
do I need to change the |
You can find a detailed a how-to run the cypress suite in https://flowfuse.com/handbook/development/frontend/testing/#e2e-integration-tests
In a nutshell, no, not only that because the cypress suite visit's the library page and after the redirect it expects to find elements of the blueprint page because that was the default up to now and fails because it can't find them.
I'm sure you'll get the gist of it once you run the e2e tests, if not, let me know and I'll help you out |
Hello @cstns,
As I am still new to tests, I think it would be better if you could help me write these tests |
I'll be more than happy to help! I'll make the changes on this PR and leave comments on the changes |
I was incapable of updating your pr and inadvertently created a new one. I marked it as draft so it won't get merged. Look over the comments and move the necessary changes here. |
@friyad, there are a couple of linting errors that prevent the e2e tests from completing successfully. I suspect they are the last thing that would need solving before accepting the PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3897 +/- ##
=======================================
Coverage 79.28% 79.28%
=======================================
Files 281 281
Lines 12755 12755
Branches 2844 2844
=======================================
Hits 10113 10113
Misses 2642 2642
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@cstns Thanks for noticing the error. I solved the lint errors. I didn't change any files there. I think these errors are coming after the merge. I also ran the e2e test. But, I am getting this error. I need your help with this:
|
Please push the changes with the merge included, I need to see the code |
Looks good, happy to approve! |
Thanks a lot @cstns, @joepavitt and @ZJvandeWeg. It was my first open-source contribution. Looking forward to contributing more. |
Description
When a user clicks on Library they see Blueprints route as default. But it should be the Team Library route. That was the problem and by this pull request, this issue has been solved.
Related Issue(s)
Issue: #3871
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
area:migration
label