New issue
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
org.astarte-platform.InterfaceName is not a valid interface name #7
Comments
Expanding on this a little bit.
Since CQL only accepts alpha-numeric characters and underscores in table names, and since sometimes the interface name has to be mapped onto a table name, we deal with it here mainly by lowercasing everything and replacing The point is, if we allow using also The first will cause conflicts between, e.g., Whichever way we decide to go, this has to be documented. |
interface name can contain hyphens everywhere but at the beginning Fix astarte-platform#7 Signed-off-by: Mattia Mazzucato <mattia.mazzucato@ispirata.com>
interface name can contain hyphens everywhere but at the beginning Fix astarte-platform#7 Signed-off-by: Mattia Mazzucato <mattia.mazzucato@ispirata.com>
interface name can contain hyphens everywhere but at the beginning Fix astarte-platform#7 Signed-off-by: Mattia Mazzucato <mattia.mazzucato@ispirata.com>
These are the examples we used to validate the regular expression for
|
interface name can contain hyphens everywhere but at the beginning Fix astarte-platform#7 Signed-off-by: Mattia Mazzucato <mattia.mazzucato@ispirata.com>
Interface name validation should allow names such as
org.astarte-platform.InterfaceName
.The text was updated successfully, but these errors were encountered: