NASA-AMMOS / NASA-AMMOS/MMGIS

[New Feature]: Separate layer variables for FeatureID, mouseover, and onClick

Open
#560 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog enhancement
Dominant language
JavaScript
Stars
232
Forks
77
Avg merge
3d 6h
Merged PRs (30d)
17

Description

Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

The "useKeyAsName" layer variable is used for mouseover events and for the Feature ID (unique value at top) in the Info tool. If that property is not meant as a Feature ID, e.g. it contains HTML, it becomes unusable for a Feature ID.

Describe the feature request

I'd like to have separate variables for Feature ID, mouseover, and feature
"onClick" events. Something like:
"useKeyAsName" = For Feature ID
"useKeyAsDisplay" = shows property(s) as a mouseover popup
"useKeyAsID" = uses this property as the unique Feature ID in the Info Tool.

Default option (i.e. no variables defined) works as always with the first feature property for all three events. For backward compatibility, "useKeyAsName" could be kept for mouseover events, but let the first feature property always be the first property in the file.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating useKeyAsName and its consumers for mouseover events, onClick behavior, and the Info Tool's Feature ID. Done means separate variables control those three uses while the default behavior and backward compatibility described in the issue remain intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.