| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I've been thinking about this one for the last 9 days and I think the solution I'm aiming to go for is instead of modifying Result to check for tags, is to add a new decorator that is injected when tags is enabled that overrides this method to provide this extra functionality. |
Sorry, something went wrong.
|
No problem, sounds like a neater way of doing it 👍 |
Sorry, something went wrong.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sorry, something went wrong.
|
Reopening as a reminder about the decorator plan since I don't see an attached ticket. |
Sorry, something went wrong.
…that option first
This switches the implementation to use a decorator which is only added when the `tags` option is set during initialization. Functionally it has no change on the effect but it allows for the logic to be more isolated. In the end it just keeps it more organized and works towards cutting back on what is included in the core results. This also changes the call for setting the `select2-data-tag` attribute to properly set the attribute as a string instead of relying on the boolean to string conversion.
…t2#5812) * refactor: check for unselected options when using tags and highlight that option first * Switch to using a decorator for highlighting tags This switches the implementation to use a decorator which is only added when the `tags` option is set during initialization. Functionally it has no change on the effect but it allows for the logic to be more isolated. In the end it just keeps it more organized and works towards cutting back on what is included in the core results. This also changes the call for setting the `select2-data-tag` attribute to properly set the attribute as a string instead of relying on the boolean to string conversion. * Fix tabbing in newly added decorator * Add tests for tag focusing in results Co-authored-by: Kevin Brown <kevin@kevin-brown.com>
…t2#5812) * refactor: check for unselected options when using tags and highlight that option first * Switch to using a decorator for highlighting tags This switches the implementation to use a decorator which is only added when the `tags` option is set during initialization. Functionally it has no change on the effect but it allows for the logic to be more isolated. In the end it just keeps it more organized and works towards cutting back on what is included in the core results. This also changes the call for setting the `select2-data-tag` attribute to properly set the attribute as a string instead of relying on the boolean to string conversion. * Fix tabbing in newly added decorator * Add tests for tag focusing in results Co-authored-by: Kevin Brown <kevin@kevin-brown.com>
| Back | FazBrowse Home | New Git URL |
This pull request includes a
The following changes were made:
This works at the moment when no tags exist, but not when there are existing selected tags.
Fix
Current