-
Notifications
You must be signed in to change notification settings - Fork 209
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
Completion Of $step
helper method
#833
Comments
@jywarren @publiclab/is-reviewers new issue for testing and docs for |
I guess the documentation part can be an |
@harshithpabbati if you want to split up both the issues or any one, please note that the documentation issue should be formatted into a |
@harshithpabbati? Are you going to break this issue up? |
Sorry I am traveling back to my home. So i can't work at this time. |
Ok np. |
@mgroovyank would you like to work on any one(or both) part(s) of this issue? |
Documentation issue open #885 |
I would like to work upon writing the UI tests for it. |
Thanks! Do you need any information about it? |
I will be exploring a bit and then discuss here,🙂 |
Ok.😊 |
@harshkhandeparkar there are some things that are breaking out the code maybe, can you have a look at them. It was a huge PR and congrats for the merge. @jywarren maybe we can revert the changes here now, and once we can have the things fixed we can remerge . |
Also just one thing more that also due to $step method not available in intermediateHtmlui.js 2). Also after refreshing the page, the url is correct but the steps inside url are not getting loaded. 3). I figured it out and what's happening is inside, defaultHtmlStepUi.js: if (step.linkElements[index].contains(imgthumbnail))
step.linkElements[index].href = step.imgElement.src;
} at the time of checking the condition, step.linkElements[index] is unavailable, maybe some async stuff here. @harshkhandeparkar maybe we can get this fixed here and @jywarren if we can have a revert so that we can have the code cleanup issue go on and once this gets fixed we can continue but again great work Harsh. |
What is broken?
…On Tue, 25 Jun, 2019, 10:39 PM Slytherin, ***@***.***> wrote:
Reopened #833 <#833>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AIJI5H5OJ6NKNRYZ2SUQGADP4JGL3A5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSFKY2JQ#event-2438303014>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIJI5H5GLGIVM3XJBIOBOQTP4JGL3ANCNFSM4G3ZKFQA>
.
|
Right now, the inserStep button is not working and showing this error. Also, I am seeing this error, in the console on starting up the server . |
I am pretty sure that $step is available in the intermediateHtmlStepUi.js. Maybe a recent commit broke this. |
Can you tell which line throws the not defined error by expanding it? |
@harshkhandeparkar its line 273 of defaultHtmlStepUi.js : if (step.linkElements[index].contains(imgthumbnail))
step.linkElements[index].href = step.imgElement.src;
} and step method is not working in line 92 in IntermediateHtmlStepUi.js where its showing $step is not defined. |
Ok ty. I will look into this but I won't be able to push anything today.
And we don't have to revert this. Reverting just creates a new PR, does not
react directly. I will open a new PR.
…On Tue, 25 Jun, 2019, 11:00 PM Slytherin, ***@***.***> wrote:
@harshkhandeparkar <https://github.com/HarshKhandeparkar> its line 273 of
defaultHtmlStepUi.js :
if (step.linkElements[index].contains(imgthumbnail))
step.linkElements[index].href = step.imgElement.src;
}
and step method is not working in line 92 in IntermediateHtmlStepUi.js
where its showing $step is not defined.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AIJI5H7WEUUTCQ4WLWPV7LDP4JI2DA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYQ72XA#issuecomment-505544028>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIJI5H7KDSZW43YJGRYCB4TP4JI2DANCNFSM4G3ZKFQA>
.
|
Actually, I was suggesting a revert so that I can work on things till then as I was to work upon the same functionality and I won't be able to work without it done. Is that ok to you? |
Ypu can locally revert. Reverting globally will cause problems to my branch
and pushing again will be a problem.
…On Tue, 25 Jun, 2019, 11:05 PM Slytherin, ***@***.***> wrote:
Actually, I was suggesting a revert so that I can work on things till then
as I was to work upon the same functionality and I won't be able to work
without it done. Is that ok to you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AIJI5H2QH54JDWS36NOBFYDP4JJPTA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRAMAI#issuecomment-505546241>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIJI5H4EVSX2QRUWIYB5IVTP4JJPTANCNFSM4G3ZKFQA>
.
|
Since I am also going to work on UI, so it would be better if I work on the latest code. |
If it is reverted globally, I won't be able to rebase my branch becuase
rebasing will delete the code. Oh wait, fo you know a fix for this? You can
directly push that fix or use it as a workaround locally. (I have done this
many times)
…On Tue, 25 Jun, 2019, 11:08 PM Slytherin, ***@***.***> wrote:
Since I am also going to work on UI, so it would be better if I work on
the latest code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AIJI5H44X2G5A2E7CKOYXQTP4JJXVA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRAR7Q#issuecomment-505547006>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIJI5HZ4HANZBSXRKUSXIXLP4JJXVANCNFSM4G3ZKFQA>
.
|
Actually, I don't have the fix now and working without the fix may lead to issues later . |
Ok . As you say. Let's wait for @jywarren's thoughts on this.
…On Tue, 25 Jun, 2019, 11:12 PM Slytherin, ***@***.***> wrote:
Actually, I don't have the fix now and working without the fix may lead to
issues later .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AIJI5H3JGQXQP4N45DYVPJTP4JKJBA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRA7QY#issuecomment-505548739>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIJI5HZSLRVK55UKNDNF553P4JKJBANCNFSM4G3ZKFQA>
.
|
Ya sure!! |
How complex is the fix? We haven't pushed this to the live demo yet... would it be something we can patch relatively quickly? |
I am not sure on this. Maybe @harshkhandeparkar can help on this.. But I suggest a revert so that new works by other people can go on smoothly for the time being. @jywarren |
Can you merge a short-term commenting-out of the line that causes the
error, or reverting just that line? Many lines from this code were just
shortening from more verbose commands and we could just switch back to the
longer forms until this is fixed?
…On Tue, Jun 25, 2019 at 4:52 PM Slytherin ***@***.***> wrote:
I am not sure on this. Maybe @harshkhandeparkar
<https://github.com/HarshKhandeparkar> can help on this..
Also till that I am on halt as I also have to work on things built over
that functionality.
So for the time being, I will discuss with aashna on the UI testing..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AAAF6J2NMUUCU2SJDDPSV43P4KAOJA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRR2WA#issuecomment-505617752>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J2JBGTZM7S3CTLCVHTP4KAOJANCNFSM4G3ZKFQA>
.
|
Ok trying it now!! |
I tried it and on reverting the complete intermediate file gave me the correct result. |
Sure! That would be great. And if you want to add explanatory comment and
perhaps even leave in the commented out previous line so we are super clear
this is a temporary fix. And - can you bump the 0.0.x version in your PR so
we can release it as a patch as per semver.org ? Thanks!
…On Tue, Jun 25, 2019 at 6:13 PM Slytherin ***@***.***> wrote:
I tried it and on reverting the complete intermediate file gave me the
correct result.
@jywarren <https://github.com/jywarren> do you want me to send a PR for
that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AAAF6J6JJEUVDHDZ3G3DALDP4KJ7JA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRX45I#issuecomment-505642613>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J4T55AMJH6AE42FMALP4KJ7JANCNFSM4G3ZKFQA>
.
|
Can you please explain a bit on the bump part? |
Ah, sorry - just change the version number in /package.json by one
"patch-level" interval, so increasing from 3.5.0 to 3.5.1 -- this signals
to dependencies that /use/ image-sequencer that we are releasing a bugfix!
https://semver.org has explanation of this versioning scheme which is known
as "semantic versioning" -- 0.x.0 denotes a new feature that does not break
or change any existing functionality, and x.0.0 denotes a breaking change
(a major release) which will require refactoring by "downstream" libraries
that use this one. So we're just doing a "patch-level" release, which
affects 0.0.x. Does that make sense?
…On Tue, Jun 25, 2019 at 6:28 PM Slytherin ***@***.***> wrote:
Can you please explain a bit on the bump part?
I am totally unaware of that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#833?email_source=notifications&email_token=AAAF6J3XJSBONM3YIRTLLBLP4KLVDA5CNFSM4G3ZKFQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRYYVI#issuecomment-505646165>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J3D3FUWOM63UMA2NG3P4KLVDANCNFSM4G3ZKFQA>
.
|
Yes and thanks a lot for this great information. |
scopeQuery
I have an open PR #710 which refactors the UI code by adding a new helper method called
scopeQuery
which returns a scopedjQuery
object(here it is assigned to a variable called$step
) which only searches elements inside a given scope(DOM element). This method itself is complete but needs a test and needs to be documented.Tests
The helper method is awesome and can shorten the UI code significantly but it should have a test which checks if it works properly so that the UI code doesn't break. I don't have much experience with jasmine(which is used to test UI code). If someone can add the test for me then it would be really great.
Documentation
Such a useful helper method should definitely get the attention of the contributors. It should be documented in the CONTRIBUTING.md file. If someone can do that as well, it would be great!
I Need Help
I am very busy and I want to get my PR merged but it should not be incomplete. If some contributor(s) can help me with the testing and documentation then I would be really grateful. All the information about this method can be found in the PR #710. If you are going to contribute to the tests then you can merge my branch into yours.
Note: All the 3 PRs will be merged together.
Break Me Up
This issue consists of two parts i.e. documentation and testing. Those two things are different enough from each other to deserve a dedicated issue for each. If you would like to break this issue into two separate ones it that would be helpful as well. Alternatively you can also solve one or both of these issues without breaking them up. Just let us know down in the discussion (comments).
Separated Issues:
scopeQuery
helper method #885)Resolved Issues
Open PRs
$step
method #710)$step
method #710)Thank you!
Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.
To learn how to write really great issues, which increases the chances they'll be resolved, see:
https://publiclab.org/wiki/developers#Contributing+for+non-coders
The text was updated successfully, but these errors were encountered: