We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
customDataMapper seems too generic. What about using a more significant name ?
The text was updated successfully, but these errors were encountered:
Sounds reasonable, yes. Especially considering it may be an option Sf implements someday.
For insights, this is about the option name in the ApiType.
Please notice this should not be done before v1.0.0.
Sorry, something went wrong.
Merge pull request biig-io#55 from Nek-/feat/change-the-way-to-config…
7bd99e8
…ure-the-documentation-controller
No branches or pull requests
customDataMapper seems too generic. What about using a more significant name ?
The text was updated successfully, but these errors were encountered: