Show HN: Versioned structured data, with change-request mechanic, at scale (copernic.space) 2 points by amirouche 6y ago ↗ HN
[–] larmstrong 6y ago ↗ What would an example implementation of this be? [–] amirouche 6y ago ↗ I think, I do not understand the question.The implementation is mostly in https://github.com/amirouche/copernic/blob/master/copernic/v...It used in frontend/views.pyI can elaborate on how it works if you want.Or do you mean "How a B2C or B2B product can take advantage of the change-request mechanic?". Or in other words, "How to implement change-request mechanic in another product?".
[–] amirouche 6y ago ↗ I think, I do not understand the question.The implementation is mostly in https://github.com/amirouche/copernic/blob/master/copernic/v...It used in frontend/views.pyI can elaborate on how it works if you want.Or do you mean "How a B2C or B2B product can take advantage of the change-request mechanic?". Or in other words, "How to implement change-request mechanic in another product?".
2 comments
[ 3.2 ms ] story [ 11.5 ms ] threadThe implementation is mostly in https://github.com/amirouche/copernic/blob/master/copernic/v...
It used in frontend/views.py
I can elaborate on how it works if you want.
Or do you mean "How a B2C or B2B product can take advantage of the change-request mechanic?". Or in other words, "How to implement change-request mechanic in another product?".