Everything in CAP / Java
Type
Domain
Origin
Signals
Content
Java: Answers in Java
More
Group by: None
Static check that each exported TypeScript function has a test
It reads TypeScript exports only; a project written in plain JavaScript has no exported functions for it to extract. A call to the function name in a test file counts as tested, and a call through property access such as `.foo(` does not.
ESLint rules flagging deprecated CAP configuration
Managed queues and topics over AMQP, MQTT and REST
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Regex naming rules for SAP HANA artifacts in a CAP project
Everything it checks is a name: a file name under `rootDir`, or an identifier a parser extracted from a file, so a convention that cannot be written as a regex over one name has no rule shape here. Content rules targeting `.hdbanalyticalprivilege` or `.hdbconstraint` return no results, which the README states as not yet implemented, so conventions centred on those two artifact types go unchecked.
One object page field made read-only from another's value, two ways
Neither the package manifest nor the repository tree declares a licence.
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.