Create Shorter Conflict Slugs and Recreate Slugs on Update

[harshamv]

If i have a conflicting slug it generates a very long slug as follows

Explore explore
Explore explore-7a8411ac-5af5-41a3-ab08-d32387679f2b

Is there a way i can just create 'explore-1', 'explore-2' etc.

Other option is i want to have a shorter slug generator like the following

candidates.first + friendly_id_config.sequence_separator + SecureRandom.hex(3)

How can i create a Initialization to allow this across all models?
Also how can i recreate the slug on updating a record in the model?

[xymbol]

@harshamv This is how friendly_id used to work, was lengthly discussed and, changed for a very good reason. You can always provide, say, 10 numbered candidates, and use that. This is not a general recommended solution but, might be valid in the context of your app.

[harshamv]

how can get a a fixed length of the hec value. also would like to read about the discussion and may have a valid point as well. did it happen on github discussion and can you share a link?

[xymbol]

@harshamv Don't understand your question. Please provide an example or test. As for your original question, this might work:

class Post < ActiveRecord::Base
  extend FriendlyId
  friendly_id :candidates, use: :slugged

  def candidates_with_sequence
    2.upto(10).inject([title]) { |m, o| m << "%s %d" % [title, o] }
  end
  alias_method :candidates, :candidates_with_sequence

  def candidates_with_hash
    [title, "%s %s" % [title, SecureRandom.hex(3)]]
  end
end

If any of your candidates are available, you'd still get the UUID-based conflict resolution functionality -- which is a good thing.

Re the discussion, this library has years of experience around this particular problem. We can't recall every discussion, how it originated and got resolved. This is the actual commit that introduced the current UUID-based sequencing. There's even a brief explanation in the README file.

Have you checked that already?