tmsdev / tms.select Goto Github PK

I'd love to use GroupBy a Property.

groupBy: 'Your.Package:GroupType' # If it's just a parent nodetype
groupByPropertyName: 'category'   # In addition to `groupBy`, if you'd like to group by a reference field

If only groupByPropertyName is set, it will group the Nodes only by Property maybe?

as discussed @jobee

The idea of this Issue is to have a property of the "references" type and allowing a singular choice (multiple: false|null).
To facilitate switching between singular and multiple selection afterwards.

Current Problem: Within a nodeType, when type is set to type: references and it is not multiple: true, when selecting a single entry, it doesn't apply the changes.

I will provide a snippet, if anything is unclear or needs more details, please let me know.

Thanks for the hard work and any further support is much appreciated.

 categories:
       type: references
       ui:
         label: News Category
         inspector:
           group: newssettings
           editor: 'Neos.Neos/Inspector/Editors/SelectBoxEditor'
           editorOptions:
             dataSourceIdentifier: 'tms-select-nodedata'
             dataSourceDisableCaching: true
             #multiple: true
             dataSourceAdditionalData:
               nodeTypes: ['Foo.Bar:Tag.Category']
               #startingPoint: /sites

An option to hide the current Node would be awesome.
For example we have a Document.News where you can add others Document.News as related News.
Here i'd like to hide the current Document so no relations to the current Node are possible.
@jobee

Support for type: references would be awesome

If you combineshowInCreationDialog andNotEmptyValidator the Property is visible in the Creation Dialog BUT the Validation-Warning (red Border) is not visible.

Looks like Tms.Select does not respect dimensions.

With the classic references i can only see and select Nodes which exist in the current Dimension - makes sense.

After switching to Tms.Select I can see and select Nodes which do not exist in this Dimension.
Even the Titles do not get translated.
So it looks like the "default dimensions" are used @jobee?

If you filter by keyword and add a Node, the filter remains active and can't be removed.

Lets assume we have the following Elements available

• Apple
• Pear
• Orange

How to reproduce:

1. Search for "Ora" and select the "Orange" from the filtered list
2. Click again in the searchfield - you will see "No matches found"
   Looks like the "search-filter" remains active and do not get cleared.

@jobee

It would help a lot if you could provide an example of how to use the groupBy option.

BTW: An awesome package!

If no startingPoint is set, the RootNode /sites is used as startingPoint.
This leads to unwanted effects in a multi-site setup as linking and refernces always use the actual site as startingPoint.
I can't find a way to set the startingPoint to the currently active site.

Changing the RootNode to the actual site would fix the issue: https://github.com/tmsdev/Tms.Select/blob/master/Classes/DataSource/NodeDataDataSource.php#L103

@jobee we already discussed this in Slack ☝️

By default, the Flow query will sort the results by index (position in nodetree).
We need at least two more arguments to make sorting work.

dataSourceAdditionalData:
  sortByProperty: 'title'
  sortOrder: 'ASC'

It can happen that a label has a   in it. This should be removed or replaced.