nextcloud / nextcloud/maps

Customization and priority of contact card display on maps via settings (may be willing to pay)

Open
#1,209 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

MAY BE WILLING TO PAY TO GET THIS DONE

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
The ability to add and customize contact details for both the hover-over as well as the click-event contact cards on the map. I'm looking for lots of flexibility with what goes in here and how it's displayed. I'd also like to set priority of data sources (i.e. contact card data would be displayed first followed by data obtained via forward geocoding).

The ability to update notes inside of the click-event contact bubble would be a huge plus.

Describe alternatives you've considered
I tried doing this myself and while I've successfully implemented other changes (like alternative geocoding/json parsing via Pelias) to Maps, I can't (and don't have time to) figure out how and where contact card fields are passed to Vue. I have a dev environment that I'm trying to do this in but I figured I would request this here as well. It seems like a simple change for the basics of what I'm looking for.

Additional context
Here's a sample of what I'm trying to do:

Contact Hover-Over:
fr_maps_sample1

Contact Click:
image

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

No file or test is named in the issue. Start by tracing how contact-card fields reach the Vue map UI, covering both hover-over and click-event cards. Done should include configurable contact details, source priority over forward-geocoded data, and editable click-event notes.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.