Majic Projects
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request DJPYD-5 Substitute real data with randomly generated data for identicon hash generation
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targetted for
    0.3
  • Status
    New
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (1)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    Not estimated
  • Time spent
    No time spent
    Click here to see time logged against this issue
Issue details
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates
Description
It would be useful to implement a simple mechanism (may require a model as well) that can be easily used for using random data for identicon hash instead of the original data being passed. This would include:

* Option to turn on and off such behaviour.
* Every time an identicon URL is requested for raw data, random data will be used as a hash.
* When random data is generated, then it will be mapped to raw data via database model for future (re)use.

The tricky part will be how to store the raw data in database. It may be necessary to have something a bit more complex (foreign key to some other model, and name of that model's property that's supposed to be tied-in to random data).
Comments ()
History