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

Instance API design

Open
  • Is something wrong?
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend, web-dev

Research direction

No file, test, or implementation entry point is named. Start by locating the public Sinomap instance API and the existing layers API, then determine how update, destroy, and dynamic data changes should interact. Done means the instance API design is agreed and its behavior is specified clearly enough to implement.

Written by the indexing model from the issue text.

Description

For now we can only get new Sinomap instances, without public methods updating them. Imaging some of them:

  • sinomap.update() updates map config, e.g., background color or size.
  • sinomap.destroy() removes the map.

To dynamically update data, for now we use layers. Still looking for approaches combining layers API with sinomap instance method. Any ideas?

Dominant language
JavaScript
Stars
106
Forks
14
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 doodlewind/sinomap

All issues in doodlewind/sinomap

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.