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

Change the way suggestions are displayed #32

Open
hpoom opened this issue Dec 2, 2014 · 13 comments
Open

Change the way suggestions are displayed #32

hpoom opened this issue Dec 2, 2014 · 13 comments

Comments

@hpoom
Copy link

hpoom commented Dec 2, 2014

As suggested in issue #31 I think we should move away from a popup and instead expand out the warnings that appear to show more information on the warning.

@basicallydan
Copy link
Owner

I agree. A whole new page would be a good idea but only if you can quickly go back to your lint results. The way it works atm should be easy to extend a bit.

If not the popup will probably get too big!

@hpoom
Copy link
Author

hpoom commented Dec 3, 2014

How about we have a suggestions folder, we then have each suggestion in a Markdown file. One file per suggestion. These can then be edited and maintained. We can then pull that markdown either into the CLI or into the GH Pages by using a markdown to HTML converter.

We can then use these suggestions with the popup for now, but easy to change and use in another way. Maybe an collapsible suggestions off the warnings? http://getbootstrap.com/javascript/#collapse

@basicallydan
Copy link
Owner

Yes, that would work fine - although I'm not sure whether it'd look good on the CLI, so to start with just getting it in gh-pages would do!

As for using the Bootstrap collapsible, this also sounds like a good plan :)

@piperhaywood
Copy link

I might just try to take a quick look at this as part of a 24 Pull Requests event! First time looking at an issue on an open source project... :)

@basicallydan
Copy link
Owner

@piperhaywood Welcome to open source! And great, go for it. If you wanna discuss anything lengthy or overly technical feel free to do so here, its good to have a paper trail - for more quick questions which maybe don't need to be on github https://gitter.im/basicallydan/forkability is better :) me and @M-Zuber often hang out there.

Also, thanks for showing an interest in contributing!

@M-Zuber
Copy link
Collaborator

M-Zuber commented Dec 6, 2015

I second @basicallydan.
Welcome to the wonderful world of open source.
Happy to help out with anything you need.

p.s. feel free to ping me if you are interested in help on other projects as well

@piperhaywood
Copy link

@basicallydan @M-Zuber Thanks very much! Got a little ways with it yesterday, I'm hoping to take a further look at it shortly and submit a PR later this week :)

@M-Zuber
Copy link
Collaborator

M-Zuber commented Dec 6, 2015

Great! Thank you for the update.
If you want any feedback on the code, even if you think it is not ready to merge, just open a PR with [WIP] in the title

@basicallydan
Copy link
Owner

👍 to @M-Zuber's comment.

@M-Zuber
Copy link
Collaborator

M-Zuber commented Dec 27, 2015

Hello @piperhaywood,
Just checking in. I am aware that there is such a thing as life, so please do not feel pressured.

@piperhaywood
Copy link

Thanks for checking in! I've been visiting my folks in the states for
the holidays and have been pretty lax with projects and such. Will try
to take a look when I'm back!

On 27/12/2015 09:17, Mordechai Zuber wrote:

Hello @piperhaywood https://github.com/piperhaywood,
Just checking in. I am aware that there is such a thing as life, so
please do not feel pressured.


Reply to this email directly or view it on GitHub
#32 (comment).

@basicallydan
Copy link
Owner

@piperhaywood No problem, I've been in almost exactly the same position. Hope you had a good break 👍

@M-Zuber
Copy link
Collaborator

M-Zuber commented Jan 6, 2016

Have fun!!

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

No branches or pull requests

4 participants