Patch release v2.0.3

Bug fixes

• Using h2Disk as devDatabaseType now works
• Disallowed UAA apps with skipped user management

Patch release v2.0.2

Added react reserved keywords

Patch release: v2.0.1

Fixed bug when generating entities passing an invalid (falsy) application path
Added the forgotten method to export entities by application

Major Release: v2.0.0!

Breaking changes

• JDL:
  • JHipster prefixes, entity table names, and option values respect this regex: [A-z][A-z0-9_-]*
• API:
  • JHipsterEntityExporter:
    • filterOutUnchangedEntities and createJHipsterJSONFolder have been removed
  • JHipsterBinaryOptions:
    • BINARY_OPTIONS has been replaced by Options
    • BINARY_OPTION_VALUES has been replaced by Values
  • JHipsterUnaryOptions:
    • UNARY_OPTIONS has been replaced by Options
    • The accessor has changed
      • Instead of using JHipsterUnaryOptions.Options.SKIP_CLIENT, the new way of accessing is JHipsterUnaryOptions.SKIP_CLIENT
  • JHipsterFieldTypes:
    • COMMON_DB_TYPES has been replaced by CommonDBTypes
    • CASSANDRA_TYPES has been replaced by CassandraTypes
  • JHipsterDatabaseTypes:
    • Every database type has been replaced by its uppercase counterpart
      • sql -> SQL
    • The accessor has changed
      • Instead of using JHipsterDatabaseType.Types.SQL, the new way of accessing is JHipsterDatabaseType.SQL
      • The same goes for isSql
  • JHipsterRelationshipTypes:
    • The accessor has changed
      • Instead of using JHipsterRelationshipTypes.RelationshipTypes.MANY_TO_MANY, the new way of accessing is JHipsterRelationshipTypes.MANY_TO_MANY
      • The same goes for exists
  • JHipsterValidations:
    • The accessor has changed
      • Instead of using JHipsterValidations.Vaidations.REQUIRED, the new way of accessing is JHipsterValidations.REQUIRED`
      • The sames goes for exists and needsValue
  • Deprecated objects/methods now removed:
    • DocumentParser::parse has been replaced by DocumentParser::parseFromConfigurationObject
    • JHipsterEntityExporter::exportToJSON has been replaced by JHipsterEntityExporter::exportEntities

What's new ☼

• The application generation using the JDL is now possible! Head to the doc page to know how to do it!

Fixes

• Fixed a bug when setting entity names for option could fail.
• Fixed a bug when enum values could not be tolerated by JHipster (if they start with a number), this is no longer allowed.

Patch release: v1.4.6

Standardized behavior when exporting JHipster entities:

• Inside a monolith app, generates all the entities in a JDL
• Inside microservice apps:
  • If an entity doesn't have a microservice option, generates the given entity in every microservice the JDL is imported
  • If an entity has a microservice option and isn't excluded in the current microservice, doesn't generate the given entity (but it gets generated in its microservice)

Patch release: v1.4.5

What's new ☼

• Added the clientRootFolder option to the JDL (#179)
• Added ApplicationTypes, FileUtils to the list of exported objects
• Added deprecation warnings (for v2.0.0), a warning is issued when using a soon-to-be-removed object/method.
• Cleaned up the code

Patch release: v1.4.4

What's new ☼

• Result is now a reserved keyword
• Deprecated the JDLParser::parse method in favor of the one taking a conf object (JDLParser::parseFromConfigurationObject). When using this project:
  • JDLParser::parse is convertToJDL
  • JDLParser::parseFromConfigurationObject is convertToJDLFromConfigurationObject

Fixes

• #173: Patterns are now correctly exported (JDL export), thanks @deepu105 for reporting this
• #176 (thanks @ruddell for reporting this):
  • When importing a JDL (without microservice option) inside a microservice app, sets up every entity for this microservice
  • Otherwise, the current behavior is kept: options are not set up automatically.

Patch release: v1.4.3

Fixes

• #169: the serviceClass option value is the default service value when filtering if no other value is set

entity A
entity B

filter A

will result in the same JSON files as (if no option is already set in the file)

entity A
entity B

service A with serviceClass
filter A

Patch release: v1.4.2

Fixed:

Blobs are now correctly imported and exported.
To fix this issue.
Thanks @gmarziou for reporting it :)

Patch release: v1.4.1

Fixed:

When exporting to JDL, the jpaMetamodelFiltering was never exported.
Considering this workflow:

• Importing a JDL file with the filter keyword
  • Generates one or more JSON file/s with the jpaMetamodelFiltering to true
• Exporting the JSON file/s to JDL
  • the jpaMetamodelFiltering was always false