-
## Description
### User story
As a Cartography team member, I want to design the interface between FE and vets-api, so that we are ready to work in parallel on multiple layers of the application…
-
**Cieľ:**
Navrhnúť API endpoint GET /users/{email} pre získanie detailov používateľa na základe jeho e-mailovej adresy v rámci realitnej aplikácie.
**Parametre:**
id (povinné): id používateľa, kt…
-
Currently the formatter is only configurable by a predefined set of options. We should design a public API allowing extensions to the formatter, so automatic formatting operations triggered by user ac…
-
# :bulb: Feature request
## Feature Name
Design API Docs Page
## The Desired Behavior
- [ ] `@daffodil/design` should have its own API docs page that's navigated through tabs on each component p…
-
We want to support writing to different sources the generated metrics, the output schema should be ideally standard and the writing mode should be "append only".
-
**Popis**
API endpoint POST /realities/{realityId} slúži na aktualizáciu detailov existujúcej nehnuteľnosti na základe jej unikátneho identifikátora. Ak je realityId prázdne (null), vytvorí sa nový z…
-
**Popis**
API endpoint GET /realities/{realityId} slúži na získanie detailov konkrétnej nehnuteľnosti na základe jej unikátneho identifikátora.
**Požiadavky**
Metóda: GET
Cesta: /realities/{real…
-
### Idea
The client generates ApiClient classes and the methods for `application/json` response and request types.
```c#
// UserClient.cs
public async Task PostUserAotAsync(TBody body, JsonTypeI…
-
Type creation is a pain point in the current Limited API. (The problems are systemic -- module spec has similar issues -- but they're most visible there & a solution should be applicable elsewhere.)
…
-
This issues proposes what the (long-term) APIs will look like. Looking for comments, nothing set in stone.
### 1. Hash engine
Tracked in https://github.com/sigstore/model-transparency/issues/140
…