Skip to main content

WebApp Front-End Submit- Provide option to create slug without timestamp

Feature

Casey Jeppesen requested this
We add timestamp automatically to front-end WebApp slugs ( probably to ensure uniqueness), but can we provide partners a way to generate more human-friendly slugs?

Posted by Matt Jones ·
3 comments

Log in to comment and vote

Comments3

  • Matt Walter changed status to In Review
    Team•

    Sep 23, 2020

    Thanks. I think we have all the info we need now.

  • Casey Jeppesen

    •

    Sep 18, 2020

    Thanks Matt. Feeding an error back saying the slug isn't unique would be preferable in our case. It's probably best for all cases, to make a uniqueSlug variable in the form configurations, and let the developers choose how they want to handle it in each case.
    ie.
    "Ensure slug is unique?"
    uniqueSlug: [disabled, appendTimeStamp, appendCount, etc]
    In the meantime, perhaps we can do a workaround with a graphql mutation. Question, what is the best way to trigger the mutation after webapp form submit?

  • Matt Walter

    Team•

    Sep 16, 2020

    Yes, timestamps are for uniqueness.
    Casey Jeppesen - What slug format would you prefer? I'm not sure that people will want us to feed an error back to the user saying a slug isn't unique, and blocking the submission by default. However, we can look at setting that up as an option.