Common structure of base libraries
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- developer-experience
Research direction
Start by reviewing the mapbox-base submodules and comparing the package layouts and namespaces of optional and variant, especially their include paths. Define a common repository structure and consistent public include and namespace conventions, then confirm that the VisionSDK use cases can consume both libraries consistently.
Written by the indexing model from the issue text.
Description
Right now mapbox-base is a set of small submodules. That makes hard to support consistency between each small repo. Maybe we should place all these files in one repo? Like a std library.
As example, in VisionSDK we want to use optional and variant from mapbox-base and have a troubles:
optionalclass is placed insidestd::experimentalnamespace, but variant places inmapbox::utilone.optionalpackage have different structure fromvariant.varianthaveinclude/mapboxfolder that allow me to add include folder toinclude_directoriesand use#include "mapbox/variant.hpp". But i can't do the same withoptional. Becauseoptional.hppplaced directly insideoptionalsubmodule directory
- Dominant language
- C++
- Stars
- 24
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapbox/mapbox-base
-
documentation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
mapbox/mapbox-base#21 · 1 comment ·
All issues in mapbox/mapbox-base
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
espressif/esp-matter#1867 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
cuAmpcorParameter.cpp (CPU pycuampcor) does not compile with libc++: EXIT_FAILURE is undeclaredOpen
Difficulty 1/5 Under an hour Newbie friendliness 92/100
isce-framework/isce3#387 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
conan-io/conan-center-index#31055 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day