You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the location (CEX) mapppings of assets to identifier per location are in huge hard coded mappings which end up in memory. We need a better solution that is only used when needed and is editable by the user.
Task
New table
Create a new table in the global DB for location asset mappings. Something like:
CREATE TABLE IF NOT EXISTS location_asset_mappings (
location TEXT NOT NULL,
value TEXT NOT NULL
target_asset TEXT NOT NULL COLLATE NOCASE,
FOREIGN KEY(target_asset) REFERENCES assets(identifier) ON UPDATE CASCADE ON DELETE CASCADE,
PRIMARY KEY (location, value)
);
Move mappings
Move all mappings from memory into that table
Create API endpoints
The user should be able to view, add and edit those mappings. So that we don't need to "fix" mappings by making new releases, but just asking the user to add it to the mapping.
Allow pulling of remote data
These mappings should also be added to our remote data pulling mechanism. So if we push an update of the mappings it's updated for all clients. Our choices should override users as there should be only one source of truth.
The text was updated successfully, but these errors were encountered:
Problem Definition
All the location (CEX) mapppings of assets to identifier per location are in huge hard coded mappings which end up in memory. We need a better solution that is only used when needed and is editable by the user.
Task
New table
Create a new table in the global DB for location asset mappings. Something like:
Move mappings
Move all mappings from memory into that table
Create API endpoints
The user should be able to view, add and edit those mappings. So that we don't need to "fix" mappings by making new releases, but just asking the user to add it to the mapping.
Allow pulling of remote data
These mappings should also be added to our remote data pulling mechanism. So if we push an update of the mappings it's updated for all clients. Our choices should override users as there should be only one source of truth.
The text was updated successfully, but these errors were encountered: