Skip to content
This repository has been archived by the owner on Dec 18, 2020. It is now read-only.

Specify monitored files by pathname #59

Open
juanmiguel431 opened this issue Aug 4, 2016 · 11 comments
Open

Specify monitored files by pathname #59

juanmiguel431 opened this issue Aug 4, 2016 · 11 comments
Milestone

Comments

@juanmiguel431
Copy link

I think it will be good idea to add the way also to could specify the path that i want this extension scan. To prevent to make a lot of clicks for every new page or file that we developed.

@MikeRogers0 MikeRogers0 changed the title Need a new feature. Specify monitored files by pathname Aug 5, 2016
@MikeRogers0
Copy link
Owner

MikeRogers0 commented Aug 5, 2016

I've updated the title to summarise the feature you're requesting :) This seems like a reasonable feature and if more users request it (By +1'ing this post), I'll implement it in the next release.

In mean meantime you can use the rel="livePage" to specify which paths to be monitored ( Like <link rel="livePage" href="/path/to/file.html" />), or limit the monitoring by type (HTML/CSS/JS).

Hope this helps :)

@Hativ
Copy link
Contributor

Hativ commented Oct 30, 2016

+1

@MikeRogers0 MikeRogers0 added this to the 2.4.0 milestone Nov 3, 2016
@MikeRogers0
Copy link
Owner

In terms of implementation, how do you feel about a whitelist/blacklist approach in the Options page?

@Hativ
Copy link
Contributor

Hativ commented Nov 3, 2016

Sounds good. How about a textarea where I can fill in the urls line-separated and two radio-buttons where I can select if its a whitelist or blacklist? Using whitelist and blacklist at the same time makes so sense, IMHO.

A url selection feature would be cool, where all fetched urls from the current site are listed, so I can select them and don't have to check developer tools or something else.

@MikeRogers0
Copy link
Owner

I think a textarea would be easiest, I'll sketch out ideas over the next month or so & put screenshots up in here :)

@MikeRogers0
Copy link
Owner

I haven't forgotten about adding this! I have some time scheduled this week (Wednesday & Saturday) to get it built. I'm also aiming to get #69 done in that time :)

@MikeRogers0 MikeRogers0 modified the milestones: 2.5.0, 2.4.0 Jan 2, 2017
@MikeRogers0
Copy link
Owner

Moved to 2.5.0, I ran out of time to get this done. Hopefully will get more time soon!

@nakwa
Copy link

nakwa commented Feb 8, 2018

Any update on this one @MikeRogers0 ? would be great! :)
beside that, is there any option available at the moment? I can't find where the rel="livePage" is documented.

@MikeRogers0
Copy link
Owner

@nakwa It's still in my backlog, but I've not forgotten! I've been very busy lately :( Though I've had a bunch of users request this feature in the last week weeks, so it's higher on my TODO list :)

rel="livePage" is documented on the options page, you use it by adding:

<link rel="livePage" href="/path/to/file.html" />

Into the head of your document :)

@MattFloyd
Copy link

I'd really like the ability to blacklist URLs. The network tab in Chrome is pretty noisy as it monitors some files that never change.

@MikeRogers0
Copy link
Owner

@MattFloyd Cool idea, I'm pretty swamped right now but that's something I reckon I could add :)

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

No branches or pull requests

5 participants