Demo: an ability to specify code with URL. about archive-website HOT 8 CLOSED

I like it. Its so handy when I want to share it with people.

from archive-website.

Yes, it's on my todo list. It's just not that simple, because rule configuration matters a lot. And we have a lot of rules and options. I don't think it all will fit on query string, so we probably need to get a database to store configuration + code and output a token.
I was planning on addressing it after v1.0.0 releases and I will find time to do a full re-write of the demo.

from archive-website.

Eek, I really wanted to keep the site static for simplicity - otherwise we will be spending time debugging why the DB connection is slow, broken, etc.

from archive-website.

from archive-website.

Yup, that's what I was referring to...why introduce something that could break? The demo isn't really meant to be anything more than just that, a demo to try it out. I think doing anything more than the query string solution is a lot of work for very little gain and maintenance headaches.

from archive-website.

My idea for this change was to turn demo into a bug reporting tool as well. It would be much easier and quicker to ask people to reproduce their issue in the demo, and past URL into github issue, then chase them for version of ESLint, .eslintrc and error messages that they are seeing.
I originally hoped to find some free service that just allows arbitrary key-value pair storage and retrieval, but I couldn't find anything out there that does this.

from archive-website.

I think that it can be easy to implement this functionality with JavaScript, due that Jekyll is a static site generator there's no other way to achieve it. We can use a library like URI.js or use plain vanilla JavaScript and window.location.href. But the steps are basically the same:

To share a link:

• Iterate over the rules to check which of them are active and store them in a dictionary
• Get the content of the editor and store it in another variable
• Convert them to an URL query using a library
• Optionally we can add an eventListener to update the website when the editor content or a rule changes but I think that it wouldn't be a good idea

To get info from a URL query:

• Parse the query and to the inverse process but checking before if a rule exists and if that's not the case append all the errors to a notification panel that can be placed above the editor

Ok, I'm sure that it wouldn't be as easy as it seems but I can try to implement it if no one is working on this, it will took me more than week but I want to try to achieve it.

from archive-website.

@guerrero the new version of the demo which is react-based is now live, so if you're still interested on implementing the "load from URL" feature, i'd say go for it!

from archive-website.