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
content_type values should be updated according to the new table names (v2_weir -> weir, v2_pumpstation -> pump etc)
The text was updated successfully, but these errors were encountered:
Should be resolved in 1D migration, but lets dubble check Didn't resolve this.
@martijn-siemerink do you think it's a good idea to modify this in threedigrid?
Sorry, something went wrong.
The content_type field is exposed to the outside (so part of the public API) and therefore we cannot change this because of backwards compatibility.
Conlcusion: no changes will be made but the usage of v2_ prefixes will be described in the documenation by @leendertvanwolfswinkel
No branches or pull requests
content_type values should be updated according to the new table names (v2_weir -> weir, v2_pumpstation -> pump etc)
The text was updated successfully, but these errors were encountered: