jhipster-core - npm Package Versions

v6.0.7

## What's new:

• JDL:
  • The min and max field validations now take decimal values (thanks to @ruddell for reporting this one):

    entity MyEntity {
      rate Double min(0.42)
    }
    

  • Constants also allow decimal values:

    MIN = 0.42
    
    entity MyEntity {
      rate Double min(MIN)
    }
    

v6.0.6

## Bug fixes:

• When exporting an application to a JDL file, the following attributes weren't quoted in the JSON file: jwtSecretKey, rememberMeKey and changelogDate. That caused the import of such a JDL file to fail because of "illegal" characters being present. Now, these options are quoted when an application is exported to a JDL file.

What's new:

• Disallowed underscores in application base names where the application is either a microservice or a UAA app.

v6.0.5

Bug fixes:

• When having a relationship like this:

  relationship OneToOne {
    A to B with jpaDerivedIdentifier,
    C to D
  }
  

  The parsing system didn't know if the comma was separating the relationship from A to B or the relationship option list.

  The comma is supposed to separate both, but a restriction has been made in this case: a comma without a new line has to separate relationship options.

  • Issue: From the generator: #10824

v6.0.4

Bug fixes:

• Authorized some relationships from & to the User entity:
  • This is in the "bug fix" section as the JDL was way too permissive and let some invalid relationships pass.
  • For Many-to-One cases:
    • if the User entity has the injected field without the skipUserMgt option set, it should fail
  • For Many-to-Many cases:
    • if there is an unidirectional relationship to the User, it should not fail as this is a valid case

v6.0.3

## What's new:

• Improved error message when having a unidirectional Many-to-Many relationship
  • Now tells the injected fields in the source & destination entities for better pinpointing.
• Added the ValidatedJDLObject, which performs validations to entities, relationships, etc.
  • The regular JDLObject doesn't do them anymore.
• Also added the ValidatedJDLOptions class
  • It has the same behavior as the ValidatedJDLOptions.

v6.0.2

Bug fixes:

• JDL export:
  • Exporting to JDL no longer validates the JDL
  • However, reimporting it can causes failures if the exported JDL has no longer supported values.
• Fixed JPADerivedIdentifier option:
  • The issue was that the exported JSON files for both entities of a relationship had the option
  • The correct way was just to have the option in the owner side of the relationship

v6.0.1

Bug fixes:

• During the JDL export, if the rememberMeKey option exists in the .yo-rc.json file, then the export failed.
  • The fix consists in ignoring it, just like the jwtSecretKey app option.

v6.0.0

Breaking changes

• JDLImporter:
  • Previously, it was a class that could be instantiated from either JDL files or string, and a configuration object.
  • Now, in order to create a JDL importer, one must use createImporterFromContent or createImporterFromFiles.
• JDLLinter:
  • Previously, it was a class that could be instantiated from JDL files.
  • Now, in order to create a JDL linter, one must use createLinterFromContent or createLinterFromFiles.
    • This adds the possibility to lint inline JDL
• JDL(entity, field, enum, etc.):
  • Removed validity check methods and moved them to the BusinessErrorChecker or their own validators.
• BinaryOptions:
  • Removed the pager value from the pagination option.
    • That was already removed from the generator when moving from bootstrap v3 to v4.

What's new

• Introduced new API, which will be the future API (for v7)
  • Used by doing require('jhipster-core').PACKAGE
  • The packages are as follows:
    • jdl: concerns the JDL (conversion, export, import, objects, linting, etc.)
    • jhipster: concerns JHipster as a whole (reserved keywords, application types, etc.)
    • json: concerns JSON-file handling (export)
      • Will be deprecated and remove if and when JHipster goes full JDL-centric
• Passing a path to the clientRootFolder is now possible
• Custom enum values are now possible:

enum Language {
  FRENCH (frenchy),
  ICELANDIC (viking)
}

Fixed

• Having a field's name starting with all... (like allowMultiple) works again
  • This was fixed by removing the all keyword from the parsing system and relying on the existing matchers to notice if the JDL file contains the "all" keyword
  • Related issue: #389
• Added missing many-to-many side when needed
  • Related issue: #352
  • This snippet didn't work before as it broke the fluent methods:

  relationship ManyToMany {
      A{b) to B
  }
  

• Fixed parsing the jpaDerivedIdentifier option
  • Related issue #388

v5.0.0

Breaking changes

• [BinaryOptions] Replaced SEARCH_ENGINE with SEARCH
• Changed the way commenting works:
  • Comments must appear before annotations, always

What's new

• Added redis and caffeine for cacheProvider (thanks to @Shaolans and @murdos)
• Custom annotations have been implemented (thanks to @yelhouti)
  • For entities, relationships and fields
• Added jwtSecretKey to the JDL
• Added option readonly to declare an entity as read only (@murdos)
• Exporting a JDL to a specific file is now possible
• Parsing a JDL as a string is possible (thanks to @deepu105)

Fixed

• Fixed detection of changed entities when custom attribute in json file (thanks to @murdos)