Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose memory budget API #1288

Merged
merged 2 commits into from
Apr 20, 2022
Merged

Expose memory budget API #1288

merged 2 commits into from
Apr 20, 2022

Conversation

evil159
Copy link
Contributor

@evil159 evil159 commented Apr 20, 2022 •
edited

This PR exposes high-level API to set the memory budget on the MapboxMap public interface.

Pull request checklist:

  • Write tests for all new functionality. If tests were not written, please explain why.
    Tests can't be written currently since there's no way to mock the MBMMap
  • Add documentation comments for any added or updated public APIs.
  • Describe the changes in this PR, especially public API changes.
  • Add a changelog entry to to bottom of the relevant section (typically the ## main heading near the top).
  • Review and agree to the Contributor License Agreement (CLA).

@evil159 evil159 enabled auto-merge (squash) April 20, 2022 08:47
@evil159 evil159 merged commit eb8c74b into main Apr 20, 2022
@evil159 evil159 deleted the rl/expose-memory-budget branch April 20, 2022 08:55
OdNairy pushed a commit that referenced this pull request Aug 22, 2023
@ZiZasaurus
Merge pull request #1288 from mapbox/zjm-MAPSIOS-308
c86c6ee 
Automation for Examples app pre-release build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@OdNairy OdNairy OdNairy approved these changes

@macdrevx macdrevx Awaiting requested review from macdrevx

@maios maios Awaiting requested review from maios

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@evil159 @OdNairy