olucurious / olucurious/PyFCM

BaseAPI.FCM_END_POINT or BaseAPI.FCM_END_POINT_BASE

Open
#368 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
814
Forks
209
PR merge metrics
No merged PRs in 30d

Description

Hi

Version on PyPI differs from master branch. I haven't explored the full branch but
master has BaseAPI.FCM_END_POINT and develop branch has BaseAPI.FCM_END_POINT_BASE

PyPI previously had BaseAPI.FCM_END_POINT but is now BaseAPI.FCM_END_POINT_BASE

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.

Research direction

Compare the BaseAPI.FCM_END_POINT and BaseAPI.FCM_END_POINT_BASE definitions across the master and develop branches, then inspect the published PyPI version. Determine which constant name is intended and document the version alignment needed; the issue is done when the branch and package behavior are consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
firebase, python
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.