Skip to content

Releases

v1.3.7

Choose a tag to compare

@sabinadams sabinadams released this 14 May 19:49

What's Changed

New Contributors

Full Changelog: 1.3.6...1.3.7

v1.3.6

Choose a tag to compare

@sabinadams sabinadams released this 07 Apr 05:11
0d0b1a0

What's Changed

Full Changelog: 1.3.1...1.3.6

v1.3.1

Choose a tag to compare

@sabinadams sabinadams released this 09 Feb 03:55

Builds and releases a set of improvements and bug-fixes

What's Changed

Full Changelog: 1.3.0...1.3.1

v1.3.0

Choose a tag to compare

@sabinadams sabinadams released this 08 Feb 08:24
748a21a

I'm happy to announce version 1.3.0 of Aurora 🎉

Major Improvement

  1. The process in which we retrieve the attributes has been updated so that it uses a more simple string-parsing method that should prevent most issues regarding missing attribute data 🎉🎉
  2. You can now use glob patterns in your aurora.config.json file thanks to @turn-a-round!

Minor Improvements

  • You can now specify multiple generators in your schemas (or no generators)
  • Field attributes on models defined in more than one file should now properly get merged together. Previously, the set defined first would be overwritten
  • Security updates

Upcoming Plans

  • Assessment of the codebase as a whole as-is and cleaning things up/documenting how things are working
  • Planning a few utility features to help manage your schema organization

If you like what I'm doing with Aurora and/or have any questions, give me a follow and check me out on Twitter

Thanks!

What's Changed

New Contributors

Full Changelog: 1.2.0...1.3.0

v1.2.0

Choose a tag to compare

@sabinadams sabinadams released this 13 Jan 01:47
01f8397

I'm happy to announce version 1.2.0 of Aurora 🎉

Major Improvement

  • Aurora will now parse every possible attribute on your models and fields 🎉🎉

Aurora previously almost exclusively used Prisma SDK's DMMF to parse out fields and models and their attributes. DMMF is incomplete however, and doesn't report EVERY possible attribute.

With a custom parser, Aurora can now parse out those values and reflect them in your generated output properly.

Screen Shot 2022-01-12 at 5 47 29 PM


If you like what I'm doing with Aurora and/or have any questions, give me a follow and check me out on Twitter

Thanks!

What's Changed

Full Changelog: 1.1.0...1.2.0

v1.1.0

Choose a tag to compare

@sabinadams sabinadams released this 02 Jan 08:41
4b725bf

I'm happy to announce version 1.1.0 of Aurora 🎉

Major Improvement

  • The @map attribute should now carry over to the generated output correctly
  • The @@index attribute should now carry over to the generated output correctly

Aurora uses Prisma's internal parser to generate the combined file. The output of that parser does not include the settings for @map and @@index in the DMMF (Data Model Meta Format).

The improvements in this release add a pre-processing bit that will parse those out in any variation.

Jan-02-2022.00-36-44.mp4

If you like what I'm doing with Aurora and/or have any questions, give me a follow and check me out on Twitter

Thanks!