profile
viewpoint
Michael van Schaik micschk Restruct web & apps Rotterdam/Leiden http://restruct.nl

micschk/chasey 1

A facebook connected game of tag

micschk/EventCalendar 1

Event Calendar module for SilverStripe CMS

micschk/fbpagefeed 1

Retrieves posts from a Facebook page for a SilverStripe site, pulling posts and storing them via CliController task

micschk/ajaxify 0

Ajaxify your entire website instantly with this simple drop-in script using the HTML5 History API with History.js and jQuery ScrollTo.

micschk/alert 0

JavaScript library to play sound alerts

micschk/backendmessages 0

DRY way to create message boxes in SilverStripe backend.

micschk/Booklet-Silverstripe-Module 0

Silverstripe module based on jQuery Plugin Booklet

issue openedsymbiote/silverstripe-multivaluefield

Get these fields updated for react/graphql rendering?

Was hoping to use KeyValueField in elemental inline (switching to non-inline editing to make MultiValueFields work). I may attempt this update myself someday but if anyone actually enjoys this react stuff I wouldn't mind if he/she beats me to it.

created time in 8 days

issue openedsilverstripe/silverstripe-tagfield

StringTagField doesn't load existing value when shouldLazyLoad is true

Following #198 & #199 , I couldn't get StringTagField to render the currently selected value when shouldLazyLoad is true. This is in an inline elemental block/react & Graphql. I do see the correct field value being returned via Graphql but the selected tags dont get rendered. This works OK when shouldLazyLoad is false (which leads me to think this might have something to do with the selected tags not being present in the options array and thus being ignored but I couldn't find out how exactly to fix this).

created time in 8 days

push eventmicschk/silverstripe-tagfield

Michael van Schaik

commit sha 07868abfb5bd8940eebb5723cb224a7fd750bc35

Adding `$schemaComponent` to make react render correct component Fixes #198

view details

push time in 8 days

issue openedsilverstripe/silverstripe-tagfield

StringTagField renders as plain Dropdown via GraphQL/react

When rendered normally, eg Gridfield detail form: Screenshot 2021-11-24 at 15 08 50

When rendered via react (elemental inline): Screenshot 2021-11-24 at 15 09 34

Seems $schemaComponent is missing in StringTagField

created time in 8 days

issue commentsilverstripe/silverstripe-framework

can't set attributes to fields in elemental

Temporary workaround (eg for placeholder attribute): $field->setSchemaData(['attributes' => ['placeholder' => 'My placeholder value']]);

sunnysideup

comment created time in 9 days

issue commentsilverstripe/silverstripe-framework

Form field attributes aren’t included in form schema

Temporary workaround (eg for placeholder attribute): $field->setSchemaData(['attributes' => ['placeholder' => 'My placeholder value']]);

kinglozzer

comment created time in 9 days

issue commentsilverstripe/silverstripe-elemental

setAttribute doesn't work in inline_editable=true

Temporary workaround (eg for placeholder attribute): $field->setSchemaData(['attributes' => ['placeholder' => 'My placeholder value']]);

lerni

comment created time in 9 days

issue openedrestruct/silverstripe-cfstreamvideo

Tag initial release

created time in 11 days

issue closedrestruct/silverstripe-namedlinkfield

Allow setting default value/values, at least for Title

Initial guess ['NamedLinkFieldName[Title]'=>'My link title'] doesn't seem to work.

closed time in 11 days

micschk

created tagrestruct/silverstripe-namedlinkfield

tag2.1.1

A SilverStripe field type for having an internal or external link *with title*, in a single field with a nicely styled form. Based on the LinkField module by Simon Elvery & Left, Right Centre.

created time in 11 days

push eventrestruct/silverstripe-namedlinkfield

micschk

commit sha c5ff6a09131492b6f138366af635317b4cc46182

Removing/Commenting-out getSchemaStateDefaults as that's probably taken care of by extending from parent FieldGroup

view details

push time in 11 days

push eventrestruct/silverstripe-namedlinkfield

micschk

commit sha 8011a91284f46b1513ffa2cfb278d39201b32112

Changing back PageID & FileID fields to Int (default 0) because as Text the TreeDropdownFields wouldn't reload their existing value if the selected item was deeper down the hierarchy

view details

push time in 11 days

created tagrestruct/silverstripe-admintweaks

tag2.1.12

Various small CMS tweaks & enhancements

created time in 11 days

push eventrestruct/silverstripe-admintweaks

micschk

commit sha d2b619d4ea9349e15cde8745fc5acdaf16b7f9e4

Minor

view details

push time in 11 days

created tagrestruct/silverstripe-namedlinkfield

tag2.1.0

A SilverStripe field type for having an internal or external link *with title*, in a single field with a nicely styled form. Based on the LinkField module by Simon Elvery & Left, Right Centre.

created time in 11 days

push eventrestruct/silverstripe-namedlinkfield

micschk

commit sha 00f04bfd6491412c28be9c74449f05bcb6c4d913

Adding react cruft (field now also works in react UIs)

view details

push time in 11 days

push eventmicschk/silverstripe-elemental

Michael van Schaik

commit sha 04955895ad1ad4c026088164bbb4143f03f683d2

Include getSummary output in graphql output by default FIX #947

view details

push time in 12 days

fork micschk/silverstripe-elemental

Create pages in SilverStripe using content blocks

http://dna.co.nz

fork in 12 days

issue openedsilverstripe/silverstripe-elemental

`getSummary()` does not function unless added from `provideBlockSchema()`

Summaries will only be included by graphql when the result of getSummary() is included from provideBlockSchema(). This doesn't seem to be documented. I'd suggest to include the summary in the block schema by default.

created time in 12 days

push eventmicschk/silverstripe-elemental-virtual

Michael van Schaik

commit sha c8d075983923b2614359f7bcff45c85c1d3212e9

Unsetting default true in AvailableGlobally $db `AvailableGlobally` being defined as default true (`Boolean(1)`) in $db causes the `$default_global_elements` config setting to have no effect (`AvailableGlobally` is always checked for new elements). Fixes #42

view details

push time in 15 days

issue openeddnadesign/silverstripe-elemental-virtual

`$default_global_elements` config setting has no effect

Because AvailableGlobally is defined as default true (Boolean(1)) in $db, setting the $default_global_elements config to false has no effect (AvailableGlobally is always checked for new elements).

created time in 15 days

issue closedsilverstripe/silverstripe-framework

NOTE: Redux Form's author advises to use React Final Form instead

Not sure if relevant for Silverstripe but on trying to update some modules to work with react rendered forms I noticed the below info on the Redux Form repo:
(probably already on the radar but leaving here just in case it was not)

⚠️ ATTENTION ⚠️

If you're just getting started with your application and are looking for a form solution, the general consensus of the community is that you should not put your form state in Redux. The author of Redux Form took all of the lessons he learned about form use cases from maintaining Redux Form and built 🏁 React Final Form, which he recommends you use if you are just starting your project. It's also pretty easy to migrate to from Redux Form, because the <Field> component APIs are so similar. Here is a blog post where he explains his reasoning, or there are two talks if you prefer video. Formik is also a nice solution.

The only good reason, in the author's view, to use Redux Form in your application is if you need really tight coupling of your form data with Redux, specifically if you need to subscribe to it and modify it from parts of your application far from your form component, e.g. on another route. If you don't have that requirement, use 🏁 React Final Form.

closed time in 19 days

micschk

issue openedsilverstripe/silverstripe-admin

NOTE: Redux Form's author advises to use React Final Form instead

(probably already on the radar but leaving here just in case it was not)

On trying to update some modules to work with react rendered forms I noticed the below info on the Redux Form repo

⚠️ ATTENTION ⚠️

If you're just getting started with your application and are looking for a form solution, the general consensus of the community is that you should not put your form state in Redux. The author of Redux Form took all of the lessons he learned about form use cases from maintaining Redux Form and built 🏁 React Final Form, which he recommends you use if you are just starting your project. It's also pretty easy to migrate to from Redux Form, because the <Field> component APIs are so similar. Here is a blog post where he explains his reasoning, or there are two talks if you prefer video. Formik is also a nice solution.

The only good reason, in the author's view, to use Redux Form in your application is if you need really tight coupling of your form data with Redux, specifically if you need to subscribe to it and modify it from parts of your application far from your form component, e.g. on another route. If you don't have that requirement, use 🏁 React Final Form.

Just in case Silverstripe is using davidkpiano/react-redux-form instead(?), that shows a similar notice:

⚠️ This project is in maintenance mode only. Please consider using Formik instead.

Adding this issue here, closing previously opened issue on silverstripe/silverstripe-framework.

created time in 19 days

issue commentsilverstripe/silverstripe-framework

NOTE: Redux Form's author advises to use React Final Form instead

Hmm the notice above may not actually be from the 'Redux Form' library Silverstripe is using (not sure).
Instead that might be davidkpiano/react-redux-form(?), which shows a similar notice:

⚠️ This project is in maintenance mode only. Please consider using Formik instead.

micschk

comment created time in 19 days

more