lorddaedra

So my idea: set `page_component` on view level or set dict with pairs `url_pattern` (or `view name`): `page_component` and load first level components dynamically for all pages.

I suggest to add this feature: ``` UNICORN = { "DEFAULT_COMPONENT_NAME": '', # empty str by default (same behaviour) or in format 'some.module:function', function MUST accept view } ``` for...

1. I like idea of dynamic components. Something like https://v3.vuejs.org/api/built-in-components.html#component I think this is required feature for some complex projects. 2. About `DEFAULT_COMPONENT_NAME_GETTER` - it's just one of the possible...

I think this is also related topic https://github.com/adamghill/django-unicorn/issues/183

Just use functions...

I suggest to update package and follow https://www.djangoproject.com/download/ Supported Django versions: Django 1.8 LTS, 1.10, 1.11 LTS. For now looks like this package is broken in 66,67% of supported configurations...

Suggestions: 1. Support matrix: - add support for Python 3.6-3.10 - add support for Django 2.2, 3.1 and 3.2 - drop support for Python < 3.6 - drop support for...

I update my suggestions: 1. Support matrix: Django 2.2 LTS + Python 3.6, 3.7, 3.8 and 3.9 Django 3.2 LTS + Python 3.6, 3.7, 3.8, 3.9 and 3.10 Django 4.0...

Okay, I fixed it via code in Nodejs Dockerfile https://github.com/nodejs/docker-node/blob/3ffba881ad5a78d33b8edf888d5406222b60686e/4.8/alpine/Dockerfile#L31,L32,L33 I suggest to copy it to Python image too...

@khairnarsaurabh23 Sorry, I don't understand your question. This is just feature request without any other related issues. Nice to have ability to use object `id`s/`uuid`s or may be pairs of...