in all type-generating functions. This can lead to errors since words like User would become aUser, while words like Umbrella would also wrongly become aUmbrella.
In our app, we had a lot of types starting with the word Upload and it was a bit weird to see aUpload in all generators. For this reason, allowing the user to specify the prefix (while defaulting to what's already present) can help combat problems like that, while giving more flexibility.
At minimum, allowing the user to turn on or off this feature would be great!
By default, the plugin specifies the prefix:
afor constantsanfor some vowelsin all type-generating functions. This can lead to errors since words like
Userwould becomeaUser, while words likeUmbrellawould also wrongly becomeaUmbrella.In our app, we had a lot of types starting with the word
Uploadand it was a bit weird to seeaUploadin all generators. For this reason, allowing the user to specify theprefix(while defaulting to what's already present) can help combat problems like that, while giving more flexibility.At minimum, allowing the user to turn on or off this feature would be great!