Skip to content

Latest commit

 

History

History
97 lines (63 loc) · 2.71 KB

CHANGELOG.md

File metadata and controls

97 lines (63 loc) · 2.71 KB

Changelog

[19.7.5] (2023-10-16)

  • Added sortRaw and fieldsRaw

[19.7.2] (2023-08-17)

  • Added userIdFieldName (default is user_id) for redefining the user ID field name in the check owner procedure

[19.7.1] (2023-08-17)

  • Added leftJoinDistinct boolean for avoid duplicates on leftJoin

[19.6.2] (2023-07-23)

  • Update linkedind login flow

[19.5.8] (2023-07-15)

  • Added leftJoin to join/joinByDemand section:
  join: [
    {
      table: 'coffee_groups',
      where: 'coffee.id = coffee_groups.coffee_id',
      leftJoin: 'groups ON groups.id = coffee_groups.group_id',
    },
  ],
  joinOnDemand: [
    {
      table: 'tea_groups',
      alias: 'groups',
      where: 'tea.id = tea_groups.tea_id',
      leftJoin: ['groups', 'groups.id', 'tea_groups.group_id'],
    },
  ],

[19.5.7] (2023-07-15)

  • Added alias as a key in relations

[19.5.5] (2023-07-09)

  • Added the SOFT_DELETE_USERS parameter to allow password restoration for deleted accounts

[19.5.3] (2023-07-09)

  • Added _join query for joinOnDemand flow in getById method

[19.5.2] (2023-07-09)

  • Await for the e-mail send method

[19.5.1] (2023-07-02)

  • Added a new unsubscribe route DELETE /emails/subscribe and subscribe route POST /emails/subscribe
  • Changing email requires confirmation using POST /login/email with the code parameter

[19.4.5] (2023-07-02)

  • Update the relations by setting the relation_field_name as an optional key in the results.

[19.4.4] (2023-06-26)

  • The new parameter joinOnDemand has been added to the definitions. It allows you to select which table to join using the _join parameter in queries. Here's an example of how to use it:
joinOnDemand: [
  {
    table: 'lang',
    where: 'lang.key = table.description'
  }
]

In this example, the joinOnDemand parameter specifies that the lang table should be joined based on the condition lang.key = table.description.

To retrieve the result with the joined lang table, you can make a request like this: GET /tables?_join=lang

This request will perform the join operation and include the joined data from the lang table in the response.

[19.4.2] (2023-06-26)

  • add encodeURIComponent posibility to email templates. Example of usage: '{{{email}}}'

[19.4.1] (2023-06-25)

  • Add the /drawio endpoint to retrieve the database schema as a CSV file that can be imported into draw.io.

[19.3.1] (2023-06-25)

  • Move the connection to the database flow to the constructor.
  • Add api.initRoutes(flow) to initialize any routes flow before starting the server.
  • The flow parameter can now be a function that takes the api object as a parameter.
  • Add the api.startServer() method.