[go: nahoru, domu]

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

Modification as mentioned in feature request #1518 #1142

Closed
wants to merge 4 commits into from
Closed

Modification as mentioned in feature request #1518 #1142

wants to merge 4 commits into from

Conversation

mebjas
Copy link
Contributor
@mebjas mebjas commented Apr 17, 2014

Signed-off-by: A V Minhaz <minhazav@gmail.com>
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling e219927 on mebjas:QA_4_1 into 237e8a5 on phpmyadmin:QA_4_1.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.01%) when pulling e219927 on mebjas:QA_4_1 into 237e8a5 on phpmyadmin:QA_4_1.

if($(this).val().length > 0)
{
bool = true;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Good to see your second commit before some one ask to do those wrappings. Can you modify your if block as well ? See other if blocks in the same file. Use a space before opening curly braces where applicable.

Signed-off-by: A V Minhaz <minhazav@gmail.com>
@mebjas
Copy link
Contributor Author
mebjas commented Apr 17, 2014

@WhaleWatching , in which case this would trigger confirm dialog against the expected behavior?

@WhaleWatching
Copy link
Contributor

Ok, for example
image
Expected behavior is type table name and click "GO" button, it shouldn't trigger confirm box.

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling ad90288 on mebjas:QA_4_1 into 237e8a5 on phpmyadmin:QA_4_1.

Signed-off-by: A V Minhaz <minhazav@gmail.com>
@mebjas
Copy link
Contributor Author
mebjas commented Apr 17, 2014

Oh its my bad..
Have a look, I have corrected it!
Thanks

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling de6743c on mebjas:QA_4_1 into 237e8a5 on phpmyadmin:QA_4_1.

@lem9
Copy link
Contributor
lem9 commented Apr 18, 2014

This is a new feature so it should go to the master branch.

@mebjas
Copy link
Contributor Author
mebjas commented Apr 18, 2014

So I should send a new pull to the master?

@lem9
Copy link
Contributor
lem9 commented Apr 18, 2014

Yes, the best is to start a new branch "feature-1518" from master in your repository. In your pull request, target the master branch.

@lem9 lem9 closed this Apr 18, 2014
@mebjas
Copy link
Contributor Author
mebjas commented Apr 18, 2014

Ok I'll update the code and send a pull to master.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants