e-mission/op-admin-dashboard

Enhancement of Token Naming Convention and Addition of Test Token Marking Feature

asiripanich opened this issue · 1 comments

  • For the NREL hosted version, the tokens should begin with nrelop (e.g. nrelop_uprm_civic_<random_string>. You might want to put the prefix into the dynamic config in case other apps want to use a different prefix.
  • Another sub-feature you might want to add is the ability to mark certain tokens as "test" tokens. In practice, this just means that the tokens have the test substring in them (e.g. nrelop_program_test_<random_string>. We could just have deployers manually insert the _test_ string, but IMHO it is better to have a checkbox rather than rely on the deployer to remember how to mark test tokens

I have been handling both these requests by judicious specification of the program name but it might be better to make it more explicit for general use.

Originally posted by @shankari in #9 (comment)

This is related to #9.

@AlirezaRa94 have you looked at this issue?