Skip to content

Conversation

@oeninghe-dataport
Copy link
Collaborator

@oeninghe-dataport oeninghe-dataport commented Jan 2, 2026

Summary

The filter plugin is migrated to POLAR@3.

Instructions for local reproduction and review

  • Open snowbox.
  • Enable the layer "Anliegen (MML)" and move the map to Hamburg, Germany.
  • Use the filters and test them.

Additional hints

Layout flaws

The layout of the filter dialog is somehow broken.
It is larger than the map's height (in the snowbox).
You may scroll it, but you cannot see the bottom of the scrollbar, as it overflows.

This, however, is, as far as I can tell, not a filter-specific problem but located probably in iconMenu.
Therefore, it is not considered here.

Styling

The general styling for this component is inspired by some (deprecated) UI/UX drafts.

Date range picker

The date range picker consists of two browser-native date pickers.
This control is supported by all major browsers (https://caniuse.com/input-datetime).

This improvised date range picker already supports limiting the dates (up to or starting with today's date).
An advanced implementation (as before with Vuetify) is left open to another PR.

Relevant tickets, issues, et cetera

Closes #370

@oeninghe-dataport oeninghe-dataport added this to the POLAR@3 milestone Jan 2, 2026
@oeninghe-dataport oeninghe-dataport self-assigned this Jan 2, 2026
@oeninghe-dataport oeninghe-dataport added the refactor Refactoring of previous code label Jan 2, 2026
@oeninghe-dataport oeninghe-dataport linked an issue Jan 2, 2026 that may be closed by this pull request
@oeninghe-dataport oeninghe-dataport force-pushed the vue3/migrate-plugin-filter branch from bd44e84 to 4640a4e Compare January 2, 2026 13:02
dependabot bot and others added 2 commits January 5, 2026 17:07
Bumps [@commitlint/cli](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/cli) from 20.2.0 to 20.3.0.
- [Release notes](https://github.com/conventional-changelog/commitlint/releases)
- [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/cli/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/commitlint/commits/v20.3.0/@commitlint/cli)

---
updated-dependencies:
- dependency-name: "@commitlint/cli"
  dependency-version: 20.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@oeninghe-dataport oeninghe-dataport force-pushed the vue3/migrate-plugin-filter branch from 4640a4e to 22cd58a Compare January 5, 2026 16:09
@oeninghe-dataport oeninghe-dataport force-pushed the vue3/migrate-plugin-filter branch 2 times, most recently from a9658ca to 9a5d3cf Compare January 7, 2026 15:33
@oeninghe-dataport oeninghe-dataport force-pushed the vue3/migrate-plugin-filter branch from 9a5d3cf to 2fa72f1 Compare January 7, 2026 15:38
@oeninghe-dataport oeninghe-dataport marked this pull request as ready for review January 7, 2026 15:45
Comment on lines +72 to +76
/** @internal */
configuration,

/** @internal */
state,
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This two fields shouldn't be internal. They should be marked as @alpha (or stable API).

Copy link
Member

Choose a reason for hiding this comment

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

state seems reasonable, configuration is redundant.

@dopenguin dopenguin removed the request for review from warm-coolguy January 19, 2026 10:33
@github-actions
Copy link

github-actions bot commented Jan 19, 2026

PR Preview Action v1.8.0

QR code for preview link

🚀 View preview at
https://Dataport.github.io/polar/pr-preview/pr-436/

Built to branch gh-pages at 2026-01-23 12:52 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Copy link
Member

@dopenguin dopenguin left a comment

Choose a reason for hiding this comment

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

  • I can't seem to be able to tab through the selection of the buttons. Please take a look at this. This probably results from the <input>s being hidden and only the labels being displayed. Not sure how a ScreenReader would interpret them as well. Maybe using an actual button here seems reasonable?
  • Selecting a BlockButton makes it jiggle a bit, which is annoying. This should be fixable by reserving some space for the border.
  • Implement the old UI for layout: 'nineRegions'. As we didn't have a final draft yet, the previous layout should be available.

I've also attached a patch which adds the pointer-events to the correct elements.

🏓 @oeninghe-dataport

"types": [
"vitest/importMeta",
"vitest/jsdom",
"node",
Copy link
Member

Choose a reason for hiding this comment

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

Why is this added here? IIRC it was added on another PR as well.

* If using `string` instead of `CategoryValue`, the string is interpreted as the `value` key.
*
* @remarks
* The values listed here can be localized:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* The values listed here can be localized:
* The values listed here should be localized:

If this is not done, one would see e.g. layer.haus.category.houseType.knownValue.shed in the UI.
It also does not seem to be intended, that this is the default value. I suggest falling back to the knownValue for the category if no locale is available.

The same goes for targetProperty.

Image

`

/**
* Technical value of a feature property.
*/
value: string
Copy link
Member

Choose a reason for hiding this comment

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

It seems fitting to also allow multiple values here.

@@ -0,0 +1,55 @@
<template>
<PolarCard class="polar-filter-card">
<FilterLayerChooser
Copy link
Member

Choose a reason for hiding this comment

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

If this is not shown (only one layer configured), I'd still expect an information for which layer I am filtering.

<label class="kern-label" for="select">Fachdatensatz auswählen</label>
<div class="kern-form-input__select-wrapper">
<select v-model="model" class="kern-form-input__select">
<option v-for="layer of layers" :key="layer">{{ layer }}</option>
Copy link
Member

Choose a reason for hiding this comment

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

I'd rather like to see the name that is defined for the layer in configuration.layers like it is done in layerChooser. I doubt someone using POLAR would understand that the layer with the id '6059' is meant to show the reports in HH.

Comment on lines +40 to +42
const layerConfiguration = computed(
() => filterStore.configuration.layers[props.layer] as FilterConfiguration
)
Copy link
Member

Choose a reason for hiding this comment

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

This variable is locally created twice. Would it be intereting to move selectedLayer from FilterUI to the store and then have a getter for layerConfiguration that can be ued in FilterCategory and FilterTime?

})
/* eslint-enable no-empty-pattern */

test('Component works as expected', async ({ wrapper, coreStore, store }) => {
Copy link
Member

Choose a reason for hiding this comment

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

What is "expected"?

</section>
</template>

<script setup lang="ts">
Copy link
Member

Choose a reason for hiding this comment

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

A lot of this functionality seems overly complex compared to the previous implementation. Can you shed some light onto your thoughtprocess and why you deem this necessary?

Copy link
Member

Choose a reason for hiding this comment

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

This looks like a function that may of use in other plugins as well.

Comment on lines +72 to +76
/** @internal */
configuration,

/** @internal */
state,
Copy link
Member

Choose a reason for hiding this comment

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

state seems reasonable, configuration is redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor Refactoring of previous code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migration of Filter plugin to POLAR@3

2 participants