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

Decide and apply a global strategy to solve root field conflicts in GraphQL schemas

    Details

      Description

      We are having conflicts across product teams and the namespace solution could not be the best fit for these cases.

      Ideally we should decide either if move forward to a schema stichting solution by continue doing renames or to a federation solution.

      Current proposals are:

      1. Use namespaces in user (admin) or commerce (commerce or adminCommerce) modules
      2. Rename methods in the source to avoid conflicts
      3. Scope all method names with some information about the bundle
      4. Allow a way of renaming the graphql method name just for one method that can cause conflicts (like an annotation for example in the resourceimpl class)
      5. Register several endpoints in graphql (one just for commerce?)
      6. Do a 2 step registration to analyze conflicts first and then rename conflicts only following some rules/priorities to ensure consistent behaviour
      7. I wish I could register both and differenciate when called but as they are typed they can have different input and output types, so that's out of the possible solutions
      8. ... your idea ...

        Attachments

          Activity

            People

            Assignee:
            support-lep@liferay.com SE Support
            Reporter:
            javier.gamarra Javier Gamarra
            Recent user:
            Marta Elicegui
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Packages

                Version Package