Hook Messages

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the project documentation and tracing how livereload handles messages when used with Fabric and Growl. Clarify whether the intended result is a configurable prefix, a callback for application code, or access to the message emitter; done requires a documented and usable integration point for the selected behavior.

Written by the indexing model from the issue text.

Description

I'm using livereload with fabric and growl - curious if it's possible to hook the message handling to integrate it a little better into my app:

  1. Reconfigure the message prefix
  2. Send a livereload message to my own function (or)
  3. Send a message to the livereload message emitter

I looked through the docs real quick but didn't see anything. Thanks!

Dominant language
Python
Stars
1.1k
Forks
149
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lepture/python-livereload

All issues in lepture/python-livereload

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.