feat(core): add MikroORM.initSync() helper
#4166
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## v6 #4166 +/- ##
==========================================
- Coverage 99.54% 99.51% -0.04%
==========================================
Files 217 217
Lines 14100 14152 +52
Branches 3238 3241 +3
==========================================
+ Hits 14036 14083 +47
- Misses 60 66 +6
+ Partials 4 3 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
B4nan
force-pushed
the
sync-init
branch
5 times, most recently
from
d521b95
to
4772b56
Compare
B4nan
added a commit
that referenced
this pull request
Apr 6, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Apr 10, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Apr 12, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Apr 26, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
May 14, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
May 14, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
May 24, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
May 26, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Jun 11, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Sep 10, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Sep 20, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Sep 24, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Sep 30, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Oct 2, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Oct 17, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Oct 21, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Oct 25, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Nov 2, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
B4nan
added a commit
that referenced
this pull request
Nov 5, 2023
As opposed to the async `MikroORM.init` method, you can prefer to use synchronous variant `initSync`. This method has some limitations: - database connection will be established when you first interact with the database (or you can use `orm.connect()` explicitly) - no loading of the `config` file, `options` parameter is mandatory - no support for folder based discovery - no check for mismatched package versions Related: #4164
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As opposed to the async
MikroORM.initmethod, you can prefer to use synchronous variantinitSync. This method has some limitations:orm.connect()explicitly)configfile,optionsparameter is mandatoryRelated: #4164