Symbol Translator

[daghovland]

AB#188605

Aim of the PR

Make the mapping from symbol name to label attributes available as JSON for the frontend.
The assumption/decision is that the symbol-library is read by the frontend, and not during translation on reception by backend

Implementation

Created a minimal asp.net web api with a single endpoint that takes a DEXPI symbol ID as its only argument and returns a json structure like this

{
  "id" : "ND0028",
  "description" : "Flow in nozzle",
  "labelAttributeA" : "<ObjectDisplayName>",
  "labelAttributeB" : "",
  "labelAttributeC" : "",
  "labelAttributeD" : "",
  "labelAttributeE" : ""
}

Also a dockerized version is made, which is now part of the docker compose setup. Test the project by starting docker compose as usual, described in docker/README.md

Type of change

• Bug fix
• New feature
• Breaking change
• This change requires a documentation update

If the changes impact any dependent services then provide details.

How Has This Been Tested?

There are github actions that test the labels A, B and C
The docker setup has been tried

Open Questions

I am not sure if this is all data that is needed for the frontend, or if the format is suitable for consumption by the frontend.

[eoye]

Very cool! Good documentation that is clear and understandable, so it was easy to test. I tested out the API and was able to get label attributes for symbol PF009A. I also tested the project by starting docker compose, and everything works👍
Nice work with the tests✔
I can't think of any other data that is needed for the frontend right now. The format looks okay to use in the frontend.