Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Naming differs from RFC standard: Notification vs. Message

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
api, backend

Research direction

Start with the terminology distinction in RFC 8030 and review the documentation changes already marked complete in this issue. Then locate the library's code references to Notification and Message and determine the full naming scope. Done means the code consistently follows the RFC terminology without leaving the documented API and implementation out of sync.

Written by the indexing model from the issue text.

Description

The Web Push protocol uses push message as description. The notification is the data transported by the push message.
The use of notification seems to be historic remnant before standardization.

I think changes should be done in two steps:

  • Change documentation
  • Change code
Dominant language
PHP
Stars
1.9k
Forks
312
Avg merge
1d 15h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 web-push-libs/web-push-php

All issues in web-push-libs/web-push-php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.