1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-22 19:07:54 +01:00
Commit Graph

12 Commits

Author SHA1 Message Date
Mateusz Kwasniewski
e32fa396fc
docs: ADR with handling tables (#5561) 2023-12-13 11:09:55 +01:00
Nuno Góis
2b5efd3883
docs: ADR: Specificity in database column references (#5499)
https://linear.app/unleash/issue/2-1680/adr-specify-tables-when-querying-columns

This PR includes my suggestion of a "Specificity in database column
references" ADR.

The ADR proposes a standard for explicitly specifying the full table
name or alias for each column in our SQL queries, especially for queries
with joins between multiple tables. This decision is a direct response
to recent ambiguity errors encountered due to a database migration,
emphasizing the need for clearer SQL query standards in complex joins
and schema changes.

---------

Co-authored-by: Mateusz Kwasniewski <kwasniewski.mateusz@gmail.com>
2023-11-30 08:36:44 +00:00
Gastón Fournier
142e322589
docs: POST and PUT body handling (#5319)
## About the changes
While working on Terraform I identified some issues with how our backend
handled some requests. This happened because the Terraform client was
unaware of new fields and was not sending them. This resulted in bad
behavior as some of those missing fields were treated in the backend as
`null` and removed existing data from the DB.

This ADR aims to shed some light on the problem and specifies how our
server should handle these requests.

---------

Co-authored-by: Nuno Góis <github@nunogois.com>
2023-11-14 07:56:58 -06:00
Nuno Góis
6b4efb9a9d
docs: ADR: Separation of Request and Response schemas (#3869)
https://linear.app/unleash/issue/2-943/adr-separate-request-and-response-types-in-apis

During the updating of our OpenAPI documentation, we've seen several
times that our schemas are either way too wide for a response or way to
strict for a request. This is usually due to us reusing the same schema
for both request and response. We should write an ADR where we reason
about the usefulness of code duplication and keeping separate response
and request schemas.

Based on our needs, this PR adds my suggested ADR.

---------

Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
2023-06-05 11:41:34 +01:00
James King
47fcc59850
docs: Fix typo in ADR (#3691) 2023-05-10 13:58:51 +00:00
Mateusz Kwasniewski
536230a364
docs: adr for db changes (#3439) 2023-04-11 14:16:40 +02:00
Thomas Heartman
5fa73b929a
Docs(fix): fix broken link to sdk-generator ADR (#2838) 2023-01-05 14:50:47 +00:00
Tymoteusz Czech
36f849e9e9
docs: Orval ADR (#2818)
https://linear.app/unleash/issue/1-537/openapi-generator-adr
2023-01-05 10:24:41 +00:00
Mateusz Kwasniewski
cc1512cd44
refactor: styled component in header (#2808) 2023-01-03 14:52:10 +01:00
Christopher Kolstad
a113f9c2c0
Change to preferred export format (#2567)
### What
This PR updates the example for the hook to use the export format that
is recommended in the ADR we've written on export types.
2022-11-30 10:42:00 +01:00
Christopher Kolstad
753d6681ff
fix typo in preferred-form-architecture (#2566)
A very quick typo fix. It's whether, not wheter. :)
2022-11-30 10:33:42 +01:00
Fredrik Strand Oseberg
ad7c139992
fix: add ADR for domain language (#2541)
This PR puts our contributing guidelines in the sidebar of the unleash
documentation. Currently there was no way of navigating to them easily,
which made our contribution guides and ADRs less useful. This PR adds
them to the sidebar as their own category, and adds an ADR for domain
centric language.

Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
2022-11-29 08:57:27 +01:00