-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
can we customize indexmap.json ? #23
Comments
I haven't added any GUI options for this, but editing indexmap is still possible. You'll have to directly modify The key of the entry to be modified is Details on what operations are done in addition to what is specified in indexmap are in https://github.com/virresh/StockD/wiki/Index-Mapping |
Ok. Bro. Thanx for that information.
i was editing indexmap.json , but now got it.
Notepad++ can do it with JSON Plugins
…________________________________
From: Viresh Gupta ***@***.***>
Sent: Tuesday, July 23, 2024 9:39 PM
To: virresh/StockD ***@***.***>
Cc: tgbssk ***@***.***>; Author ***@***.***>
Subject: Re: [virresh/StockD] can we customize indexmap.json ? (Issue #23)
I haven't added any GUI options for this, but editing indexmap is still possible. You'll have to directly modify generate_config.json (any json formatter can be used to make it human readable and any text editor can be used to edit the file). Hitting Refresh Index Mapping will revert this to it's original state though.
The key of the entry to be modified is index_map.
Details on what operations are done in addition to what is specified in indexmap are in https://github.com/virresh/StockD/wiki/Index-Mapping
—
Reply to this email directly, view it on GitHub<#23 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUAGBWAAH5M5KUXKQL7DTXDZNZ53LAVCNFSM6AAAAABLABAN5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBVGY2TONJVGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
closing as resolved |
the best |
can we customize indexmap.json ?
-Regards
tgbssk
The text was updated successfully, but these errors were encountered: