3 ms·
In your example, absolutely the first URL is better. But if as in the case of the OP, you're trying to encode an entire flowchart, I would argue it's a bit of a
by michaelmior 4y ago
In your example, absolutely the first URL is better. But if as in the case of the OP, you're trying to encode an entire flowchart, I would argue it's a bit of a pointless exercise. Maybe you could come up with something reasonably readable, but I don't think anyone would care. It really depends on what kind of state you need to store.
- moffkalast 4y agoWhoever needs to copy that long intestine of a url definitely cares.
- michaelmior 4y agoIf you can shorten the URL, sure. But if data stored in the URL means it needs to be incredibly long, I don't think most users care whether it's readable or not. Of course, at a certain length, it's worth reconsidering whether storing all the data in the URL is a good idea.
- pifm_guy 4y agoA flowchart can be encoded as simply the name of the state you're currently in.
- michaelmior 4y agoHow do you know what all the other states in the chart are and how they are connected?
- wildrhythms 4y agoHow would you predefine a state to include the flowchart nodes that the user creates?