Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-132006

Add a new field to distinguish who owns active settings

    Details

    • Type: Task
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Dataset Display
    • Labels:
      None
    • Sprint:
      S04E16 - Hard to Earn, S04E17 - Those Who Tell the..., S04E18 - Fiction and Fact, S04E19 - Takk..., S04E20 - Acabou Chorare, S04E21 - 15151, S04E22 - Ceremonials, S04E23 - Mamonas Assassinas, S04E24 - The Piano Guys

      Description

      See https://github.com/liferay-frontend/liferay-portal/pull/1047#pullrequestreview-656753920:

      If we want to use this backend service to persist state from other components, I think we should use a less opinionated field name here, something like "frontendComponentId" or similar. That would make it easier to use this entity to store active view settings for, say, a ckeditor instance (which would translate into the ckeditor config object)

      In addition, I'm in doubt about how usefiul would it be to add a "frontendComponentName" to this table, so that this field would allow to differentiate between dataset display active settings vs ckeditor active settings. I know this can be deferred to the time we add support for more than one component (hopefully soon).

       

        Attachments

          Activity

            People

            Assignee:
            ivan.zaera Ivan Zaera
            Reporter:
            ivan.zaera Ivan Zaera
            Engineering Assignee:
            Ivan Zaera
            Recent user:
            Bruno Fern√°ndez
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Packages

                Version Package