goodmap-nothingshere
goodmap plugin that shows popup if no point is visible in a view
Installation
pip install goodmap_nothingshere
Activation
Add the plugin to the plugins list in your Platzky database configuration.
The name must match the entry-point key declared in pyproject.toml:
{
"plugins": [
{
"name": "nothingshere",
"config": {}
}
]
}
Configuration
Everything under config is passed straight to the frontend component, so the popup is
tuned from the database without rebuilding the plugin. All keys are optional:
| Key | Type | Default | Meaning |
|---|---|---|---|
messages |
{ <lang>: string } |
built-in English text | Popup text per language code, picked with the site's active language and falling back to en. May contain HTML (e.g. a link). |
closeLabels |
{ <lang>: string } |
{ "en": "Close", "pl": "Zamknij" } |
Accessible name of the close button, per language. |
dismissMinutes |
number | 15 |
How long the popup stays hidden after the user closes it. A page reload also brings it back. |
{
"name": "nothingshere",
"config": {
"messages": {
"en": "No points here yet. <a href=\"/add\">Add one?</a>",
"pl": "Brak punktów tym miejscu."
},
"dismissMinutes": 30
}
}
Development
This is a goodmap frontend plugin: the backend class subclasses a goodmap capability base, and the frontend ships a React component per capability via Webpack Module Federation. A plugin declares its capabilities by subclassing one or more of:
goodmap.plugin.MapOverlayPluginBase— component mounted once over the map (exposed as./MapOverlay); this plugin's capabilitygoodmap.plugin.MarkerFieldPluginBase— component rendering/wrapping a marker-popup field (exposed as./MarkerField)
goodmap derives each capability's Module Federation module from the base class name,
so the webpack exposes keys must match, and the webpack container name must equal
the entry-point key (nothingshere). See goodmap's examples/plugins/silly-gif for
the reference layout.
Release files for goodmap-nothingshere 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| goodmap_nothingshere-0.2.0.tar.gz | 11.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| goodmap_nothingshere-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.1 kB
Release files / goodmap_nothingshere-0.2.0.tar.gz
| Download URL | goodmap_nothingshere-0.2.0.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72824a075411d81a60b303752b355b71a14ee860e72b778351ef98b2bf9c5db5
|
|
BLAKE2b-256 checksum How to use checksums |
b7a5af4a3a36f0292cb74ee330f087bf975d245631d879922f307555de8f0f4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / goodmap_nothingshere-0.2.0-py3-none-any.whl
| Download URL | goodmap_nothingshere-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23d718f871e952b3aa5e2cf3efb288cdf3938a40958924886927a6ac57182368
|
|
BLAKE2b-256 checksum How to use checksums |
5777b1db2c0de4d7ebdf62295c9535be23d71ffe16902d4a04adfd0bc9230ed1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log