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.

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

Refactor layer properties as own interface #225

Merged
merged 2 commits into from
Feb 4, 2023

Conversation

VijayanB
Copy link
Member

@VijayanB VijayanB commented Feb 3, 2023

Description

Remove unused methods
Refactor common properties

Issues Resolved

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Vijayan Balasubramanian <balasvij@amazon.com>
@VijayanB VijayanB requested a review from a team February 3, 2023 00:24
@VijayanB VijayanB self-assigned this Feb 3, 2023
@@ -48,16 +48,19 @@ export const updateLayerVisibility = (map: Maplibre, layerId: string, visibility
});
};

export interface LineLayerSpecification {
export interface Layer {
Copy link
Member

@junqiu-lei junqiu-lei Feb 3, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we name it mbLayer or add some comment here to explain it's the layer in maplibre? Because there are two layers conception: maps dashboards layer and maplibre layer

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made it local and added comment. This layer is an abstraction between Dashboard and Maplibre.

Create layer interface to abstract common properties.

Signed-off-by: Vijayan Balasubramanian <balasvij@amazon.com>
@VijayanB VijayanB changed the title Clean up unit tests Refactor layer properties as own interface Feb 3, 2023
Copy link
Member

@vamshin vamshin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks

@VijayanB VijayanB merged commit e40617e into opensearch-project:main Feb 4, 2023
@VijayanB VijayanB deleted the unit-test branch February 4, 2023 06:27
@opensearch-trigger-bot
Copy link

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-225-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e40617e17d943765a1f580c3fdbecaf66c9b7179
# Push it to GitHub
git push --set-upstream origin backport/backport-225-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-225-to-2.x.

opensearch-trigger-bot bot pushed a commit that referenced this pull request Feb 13, 2023
* Remove unused methods
* Create layer interface to abstract common properties.

Signed-off-by: Vijayan Balasubramanian <balasvij@amazon.com>
(cherry picked from commit e40617e)
VijayanB pushed a commit that referenced this pull request Feb 13, 2023
* Remove unused methods
* Create layer interface to abstract common properties.

Signed-off-by: Vijayan Balasubramanian <balasvij@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants