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

[GCI] InsertStep functionality added for loadImage step #1360

Merged
merged 11 commits into from
Dec 16, 2019
Merged

[GCI] InsertStep functionality added for loadImage step #1360

merged 11 commits into from
Dec 16, 2019

Conversation

harshkhandeparkar
Copy link
Member

@harshkhandeparkar harshkhandeparkar commented Dec 15, 2019

Fixes #1300 (<=== Replace 0000 with the Issue Number)
Fixes #1363

As I mentioned in the issue thread, I fixed the whole insert step function which was broken badly.

Here's what was broken:
broken-insert-step

When the insert step button is clicked, it generates the previews in the last step instead of the step that is clicked(This was an insertPreviews.js bug)

Fixed

fixed-insert

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

  • tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with npm test
  • code is in a uniquely-named feature branch and has no merge conflicts
  • PR is descriptively titled
  • ask @publiclab/is-reviewers for help, in a comment below
  • Insert-step functionality is working correct as expected.

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Please make sure to get at least two reviews before asking for merging the PR as that would make the PR more reliable on our part

Thanks!

@codecov
Copy link

codecov bot commented Dec 15, 2019

Codecov Report

Merging #1360 into main will decrease coverage by 0.18%.
The diff coverage is 12.5%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1360      +/-   ##
==========================================
- Coverage   66.41%   66.23%   -0.19%     
==========================================
  Files         125      125              
  Lines        2552     2559       +7     
  Branches      397      400       +3     
==========================================
  Hits         1695     1695              
- Misses        857      864       +7
Impacted Files Coverage Δ
examples/lib/intermediateHtmlStepUi.js 11.11% <0%> (-0.26%) ⬇️
examples/lib/defaultHtmlStepUi.js 10.98% <0%> (-0.4%) ⬇️
examples/lib/insertPreview.js 13.51% <28.57%> (ø) ⬆️

@harshkhandeparkar
Copy link
Member Author

This was supposed to be a one or two file PR but I ended up changing 6 files.

@harshkhandeparkar
Copy link
Member Author

This ended up being more complicated than I had initially guessed.

@keshav234156
Copy link
Member

@harshkhandeparkar Can you please open a separate issue and PR for that?

@harshkhandeparkar
Copy link
Member Author

harshkhandeparkar commented Dec 15, 2019 via email

@keshav234156
Copy link
Member

keshav234156 commented Dec 15, 2019

ok then i will open a new task please claim that also.

@harshkhandeparkar
Copy link
Member Author

harshkhandeparkar commented Dec 15, 2019 via email

@keshav234156
Copy link
Member

If you can. then go for it

@harshkhandeparkar
Copy link
Member Author

harshkhandeparkar commented Dec 15, 2019 via email

@keshav234156
Copy link
Member

It will be really difficult though. I will have to get the first pr merged while hiding the second one. Once the first one is merged, I will have to rebase the second, get it reviewed, get it merged.... It will be difficult for you too. If it is possible to review a single PR then please do so.

On Sun, 15 Dec, 2019, 11:42 PM keshav234156, @.***> wrote: If you can. then go for it — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1360?email_source=notifications&email_token=AIJI5H2AE7JDGEK7HAHJ7WDQYZXQTA5CNFSM4J3ALRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG46YAI#issuecomment-565832705>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIJI5H7IZKU3XB5PHAIIUOLQYZXQTANCNFSM4J3ALRAQ .

ok,i understand that .Will do the review in single PR

@harshkhandeparkar
Copy link
Member Author

harshkhandeparkar commented Dec 15, 2019 via email

Copy link
Member

@keshav234156 keshav234156 left a comment

Choose a reason for hiding this comment

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

1.insert step in load image is not present once you delete any step.please try to figure out.

examples/lib/insertPreview.js Outdated Show resolved Hide resolved
examples/demo.js Outdated Show resolved Hide resolved
examples/demo.js Outdated Show resolved Hide resolved
@keshav234156
Copy link
Member

1.insert step in load image is not present once you delete any step.please try to figure out.

@harshkhandeparkar
Copy link
Member Author

1.insert step in load image is not present once you delete any step.please try to figure out.

What? I didn't get you.

@harshkhandeparkar
Copy link
Member Author

Ok ok, I found the error. Fixing it now.

@keshav234156
Copy link
Member

keshav234156 commented Dec 16, 2019

@harshkhandeparkar I couldn't get why previews were not displayed in the second step ie where were we wrong.

@harshkhandeparkar
Copy link
Member Author

I managed to fix this

1.insert step in load image is not present once you delete any step.please try to figure out.

fixed-enable-disable

@harshkhandeparkar
Copy link
Member Author

@harshkhandeparkar I couldn't get why previews were not displayed in the second step ie where were we wrong.

That is because the previews were being added directly to the last step's dropdown instead of adding to the dropdown which is clicked.

@harshkhandeparkar
Copy link
Member Author

@keshav234156 I opened the new issue on request.

@jywarren
Copy link
Member

Aha! Cool, thanks for working through this. I think it needs an update (i can press the button if you like?) but just ping me when it's ready for merge and we can prioritize this! Thank you!

@harshkhandeparkar
Copy link
Member Author

This needs a mentor review, can we merge the comments PRs before this? Rebasing will be simple.

@jywarren
Copy link
Member

Comments PR? Can u point me to it? Thanks!

@harshkhandeparkar
Copy link
Member Author

PR #1343 to #1351 which are parts of the HoF task.

Copy link
Member

@keshav234156 keshav234156 left a comment

Choose a reason for hiding this comment

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

Great Work!!!!!!

@keshav234156
Copy link
Member

@jywarren we can merge this as well before update

@harshkhandeparkar
Copy link
Member Author

Thanks, @keshav234156. Should I add the label?

@harshkhandeparkar
Copy link
Member Author

is-reviewers had tried to make this a rule - always sort PRs through labels (Work-In-Progress, Needs Work, Ready-To-Merge, Small, Critical, Important, etc)

@jywarren
Copy link
Member

OK, now if we update this it should pass and we can merge 🙌

@jywarren jywarren merged commit 4a86abb into publiclab:main Dec 16, 2019
jywarren pushed a commit that referenced this pull request Dec 16, 2019
* add markuo

* add markupfix insertPreview

* fix insertPreview test

* make the new insertPreview work

* fix disabled

* small fix

* fix comments

* remove console log

* fix enabling/disabling of insert-step btn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Insert Step Previews not Working as Expected Insert Button In load image step
3 participants