Store common settings in an editable way

Open
#57 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift

Research direction

The issue names no files, tests, or entry points; start by reviewing related issues #56 and #51. Define how project-wide and case-specific settings should be stored and updated without adding optional parameters, with completion requiring a decided, usable settings design.

Written by the indexing model from the issue text.

Description

Some features contain settings that users might want to define for an entire project, or adjust in specific cases. In these cases, we don't want to add more optional parameters, but rather store and update these settings as-necessary.

Related issues:

#56
#51

Dominant language
Swift
Stars
232
Forks
51
PR merge metrics
No merged PRs in 30d

Getting set up

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 mapbox/mapbox-scenekit

All issues in mapbox/mapbox-scenekit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.