Agregar una configuración personalizada por usuario en un plugin

Wiki de la comunidad Desarrolladores
,
1

Acabo de pasar por este proceso y experimenté una serie de pruebas y errores, así que pensé en documentar mis hallazgos para ayudar al siguiente desarrollador que se incorpore.

Lo que necesité:

  • Registrar tu tipo de campo personalizado (el mío era booleano, el predeterminado es cadena)

    # plugin.rb
User.register_custom_field_type 'my_preference', :boolean

  • Registrar que el campo personalizado debe ser editable por los usuarios. La sintaxis coincide con la de params.permit(...)

    # plugin.rb
register_editable_user_custom_field :my_preference # Tipo escalar (cadena, entero, etc.)
register_editable_user_custom_field [:my_preference , my_preference : []] # Para tipo de array
register_editable_user_custom_field [:my_preference,  my_preference : {}] # Para tipo json

  • Agregarlos a los campos serializados con el CurrentUserSerializer

    # plugin.rb
DiscoursePluginRegistry.serialized_current_user_fields << 'my_preference'

  • Crear un componente para mostrar tu preferencia de usuario

    // assets/javascripts/discourse/templates/components/my-preference.hbs
<label class="control-label">¡Mis preferencias personalizadas!</label>
{{preference-checkbox labelKey="my_plugin.preferences.key" checked=user.custom_fields.my_preference}}

  • Conectar ese componente a uno de los puntos de conexión (outlets) del plugin de preferencias (el mío estaba bajo ‘interfaz’ en las preferencias de usuario)

    # assets/javascripts/discourse/connectors/user-preferences-interface/my-preference.hbs
{{my-preference user=model}}

  • Asegurarse de que los ‘campos personalizados’ se guarden en esa pestaña de preferencias

    import { withPluginApi } from 'discourse/lib/plugin-api'

export default {
  name: 'post-read-email',
  initialize () {
     withPluginApi('0.8.22', api => {

       api.modifyClass('controller:preferences/emails', {
         actions: {
           save () {
             this.get('saveAttrNames').push('custom_fields')
             this._super()
           }
         }
       })

     })
  }
}

Este documento está controlado por versiones: sugiera cambios en GitHub.

33 Me gusta
Add a plugin based custom user field to the create account form?
Problem updating user custom_fields created by a plugin
"wrong number of arguments" on Upgrade to new version
Extend Existing Controller?
Developer Index
Could a List of Recommended Topics Be Added to the Top Menu?
2

Nice! I attempted the same in GitHub - mozilla/discourse-post-read-email: INACTIVE - http://mzl.la/ghe-archive - A discourse plugin to give users the option of marking posts as read when emailed and arrived at almost the same result.

My only differences were I didn’t hunt down User.register_custom_field_type and so used my own ugly workaround. (I’ll switch to register_custom_field_type when I get the chance.)

And I think I came up with a slightly neater solution for saving the field, I patch the preferences controller to save custom fields alongside everything else, so the field is saved when the “Save” button is clicked, rather than when it’s toggled:

import { withPluginApi } from 'discourse/lib/plugin-api'

export default {
  name: 'post-read-email',
  initialize () {
     withPluginApi('0.8.22', api => {

       api.modifyClass('controller:preferences/emails', {
         actions: {
           save () {
             this.saveAttrNames.push('custom_fields')
             this._super()
           }
         }
       })

     })
  }
}

This should work for all preferences controllers, as they all seem to use saveAttrNames.

10 Me gusta
3

As a follow-up here, it turns out that inline-edit-checkbox is available only in the adminjs package, meaning this is currently Bad Advice™. I’ve resorted to using the method suggested above alongside the preference-checkbox component

{{preference-checkbox labelKey="my_plugin.preferences.key" checked=model.custom_fields.my_field}}

which works for all users.

Also, @LeoMcA, I had to modify your preferences hack slightly to work with the interface page since saveAttrNames was a computed property there.

this.get('saveAttrNames').push('custom_fields')
5 Me gusta
4

Per DEV: Allow plugins to whitelist specific user custom_fields for editi… · discourse/discourse@4382fb5 · GitHub, custom fields must now be added to a whitelist to allow editing by users. All that is needed is a single line in plugin.rb:

register_editable_user_custom_field :my_field

@gdpelican @LeoMcA I have updated the OP with this extra step, and also pulled in the comments from your second and third posts. Please feel free to update anything else you feel is necessary.

8 Me gusta
5

Perfect, thanks for this - I had fixing discourse-post-read-email on my todolist after last week’s security commit, and this makes it a whole lot easier!

Question (which may belong in a seperate post):

Will this serialize the custom field as an array, even if it only has a single element in it? I’ve been having to use the following pattern in a seperate plugin, so that:

user.custom_fields["field1"] = [ :item ]
user.save_custom_fields

becomes:

Array(user.custom_fields["field1"])
> [ :item ]

rather than:

user.custom_fields["field1"]
> :item
2 Me gusta
6

This change only deals with saving custom fields, so I don’t think it will affect how they are serialized.

That said, I do know that there are a lot of weird edge cases relating to custom fields which we are hoping to address in a few weeks time (after 2.1 is released). What you describe above looks like one of those weird cases that we need to improve.

6 Me gusta
7

Note that if the user custom field is a JSON string, you need to include the keys, or an empty hash (if the keys are dynamic), for it to be permitted, e.g.

register_editable_user_custom_field geo_location: {}
3 Me gusta
8

hm, in a slight pickle actually. If the custom field is JSON, in order to save it, you need to pass a hash, i.e.

register_editable_user_custom_field geo_location: {}

will permit

{"custom_fields"=>{"geo_location"=>{"lat"=>"-37.7989239", "lon"=>"144.8929753", "address"=>"Barkly Street, Footscray, City of Maribyrnong, Greater Melbourne, Victoria, 3011, Australia", "countrycode"=>"au", "city"=>"", "state"=>"Victoria", "country"=>"Australia", "postalcode"=>"3011", "boundingbox"=>["-37.7989854", "-37.7988961", "144.8928258", "144.8931743"], "type"=>"tertiary"}}>

However, if the param is empty (e.g. the user clears the field), the custom_field is interpreted as a string

{"custom_fields"=>{"geo_location"=>"{}"}}

and is not permitted.

There isn’t an easy way around this in the current structure, i.e. the way user_params are added to in the users_controller

permitted << { custom_fields: User.editable_user_custom_fields }

Unless I’m missing something, perhaps some additional provision needs to be made for user_custom_fields that are typecast as JSON?

1 me gusta
9

I had a similar problem with arrays, not sure if the same will work for JSON. To allow an empty array, you have to permit ‘scalar’ values as well as an array:

register_editable_user_custom_field :geo_location
register_editable_user_custom_field geo_location: []

Or if you’re feeling fancy it can be combined into one line:

register_editable_user_custom_field [ :geo_location, geo_location: [] ]

This is the same behaviour as params.permit(...), so I hesitate to call it a bug. Maybe we can call it a ‘quirk’ :wink:

Let me know if that approach works for JSON - if not we can work out another solution

6 Me gusta
10

:facepalm: of course. Just add another. It’s been a long day. Thanks!

3 Me gusta
11

Visiting this again, it feels like there are too many steps here for something that the core plugin system has a command for. On the backend, I have to write the following to make this go:

# plugin.rb
register_editable_user_custom_field :my_setting
User.register_custom_field_type 'my_setting', :boolean
DiscoursePluginRegistry.serialized_current_user_fields << 'my_setting'

but I feel like I should be able to do this:

# plugin.rb
register_editable_user_custom_field :my_setting, :boolean

You could even avoid people running into that nasty array snag by making the plugin system support the following cases:

register_editable_user_custom_field :my_setting, :array
register_editable_user_custom_field :my_setting, :object

@david

10 Me gusta
12

Este es un post muy útil que presenta un ejemplo claro de cómo configurar un campo personalizado de usuario. ¿Existe algo similar para ayudar a guiar la creación de un campo personalizado de tema sencillo? Estoy intentando resolverlo aquí:

Pero aún no he logrado que funcione correctamente. Agradecería mucho cualquier ayuda al respecto.

1 me gusta
14

David,

¿Esto ya no funciona?

Hemos estado usando:

  register_editable_user_custom_field [:geo_location,  geo_location: {}] if defined? register_editable_user_custom_field
  register_editable_user_custom_field geo_location: {} if defined? register_editable_user_custom_field

para permitir guardar un objeto json en un campo personalizado de usuario, pero esto ahora está impidiendo que los sitios se reconstruyan.

Hemos estado usando esto durante algún tiempo.

El error que obtenemos durante la compilación es:

ArgumentError: wrong number of arguments (given 0, expected 1)
/var/www/discourse/lib/plugin/instance.rb:170:in `register_editable_user_custom_field'
/var/www/discourse/plugins/discourse-locations/plugin.rb:95:in `block in activate!'

Para añadir a la confusión, esto parece funcionar en desarrollo, pero solo falla durante una compilación de producción.

Si se elimina, el sitio se compilará pero el campo personalizado del usuario no se guardará y fallará silenciosamente.

¿No veo que esto haya cambiado en años?:

¿Es una nueva versión de Rails la que lo está bloqueando ahora?

2 Me gusta
15

@Falco ¿podría estar esto relacionado con Ruby 3.x?

2 Me gusta
16

Para tu información, tengo instalada la versión 2.7.1 localmente para desarrollo (¡ups!)… ya lo estoy arreglando.

3 Me gusta
17

Sí, definitivamente está relacionado con Ruby 3.1.x. Funciona bien en 2.7.x.

2 Me gusta
18

Tengo el plugin instalado y habilitado con la configuración predeterminada en mi entorno local con el Ruby actual, ¿cómo puedo desencadenar el error?

1 me gusta
19

Bueno, ese es el problema. rbenv no me permite instalar Ruby más allá de 3.0.2 y en desarrollo (¿qué me estoy perdiendo?) no puedo provocar el error en desarrollo. Pero tan pronto como intentas compilar una instancia actual de tests-passed con el Plugin de Ubicaciones en la rama production_fixes (ignora el nombre, está rota).

1 me gusta
20

Es 3.1.3 por cierto. Si estás abierto a sugerencias, asdf me funciona muy bien.

Genial, lo intentaré.

2 Me gusta
21

Lo siento, creo que en realidad he corregido el error de compilación en esa rama. No pensé que funcionaría, pero esto, parece que al menos compila, ahora solo estoy probando la funcionalidad:

Parece que si usas este truco:

 register_editable_user_custom_field [:geo_location,  geo_location: {}] if defined? register_editable_user_custom_field

sugerido por David anteriormente, ¿funciona?

1 me gusta