Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to apply to model with existing slug property #6

Open
NightJar opened this issue Dec 29, 2018 · 0 comments
Open

Ability to apply to model with existing slug property #6

NightJar opened this issue Dec 29, 2018 · 0 comments

Comments

@NightJar
Copy link
Owner

In the case that a model has already been defined with a slug property, the addition of URLSlug is unnecessary.
Would it be possible to apply the Slug extension to such a model to utilise its generation, synchronisation, and 'state' functionality, without it also necessitating the existence of URLSlug, instead using a property of arbitrary name to store and check the generated value?

The outcome of this issue may in fact be only to update the documentation to make clear that this module does not support such a use case. However I think something could probably be achieved - but it should be balanced between code complexity and maintainability (e.g. would such a feature be rendered un-upgradable to SS5?)

Thanks to @ramono for bringing this up through a slack thread :)
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant