Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add @ for text type in tabular output #581

Closed
sirex opened this issue Mar 13, 2024 · 0 comments · Fixed by #588
Closed

Add @ for text type in tabular output #581

sirex opened this issue Mar 13, 2024 · 0 comments · Fixed by #588
Labels
format:tabular U1 Užsakymo indeksas

Comments

@sirex
Copy link
Collaborator

sirex commented Mar 13, 2024

Currently tabular formats uses flatter function, which uses . or [] separators based on value type.

For text type we need to use @ separator and for that flatten function must also get tree of types in order to choose correct separator depending on type.

For example if we have a manifest table:

d | r | b | m | property | type    | ref     | access  | level | uri
example/ascii/text/lang  |         |         |         |       | 
  |   |   | Country      |         | name    |         |       | 
  |   |   |   | id       | integer |         |         |       |
  |   |   |   | name     | text    |         | open    | 3     |
  |   |   |   | name@en  | string  |         | open    |       |
  |   |   |   | name@lt  | string  |         | open    |       |

Then query like this:

GET /example/ascii/text/lang/Country/:format/ascii?lang(*)&select(id,name)

Should return:

--  ------  ---------  -------
id  name@C  name@en    name@lt
0   LT      Lithuania  Lietuva
1   UK      England    Anglija
--  ------  ---------  -------

Related

@adp-atea adp-atea linked a pull request Mar 19, 2024 that will close this issue
@JuliusLADP JuliusLADP added the U1 Užsakymo indeksas label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
format:tabular U1 Užsakymo indeksas
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants