Added support for custom TagView subclass and default select tag action #187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here a couple of fixes.
The reason to even do subclassing - if each tags represents a model subclassing would allow associate a model with a tag and not have to match what models were selected by a string value of selected titles. For example, below is the implementation of a subclass that works with this pull request changes - each tag represents a category in this case, and there's an extension for the TagListView that returns and sets a list of categories:
Let me know what you think - happy to make changes!
Best,
Kateryna