Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 36 million developers.
Sign up
-
IBM Czech Republic
- Hradec Králové
- Sign in to view email
- https://bajtos.net
Pinned
1,914 contributions in the last year
Activity overview
Contributed to
strongloop/loopback-next,
strongloop/loopback-labs,
strongloop/loopback-datasource-juggler
and 5 other
repositories
Contribution activity
August 1, 2019
bajtos has no activity
yet for this period.
July 2019
- bajtos/graphql-workshop-july-2019 TypeScript
Created a pull request in strongloop/loopback-next that received 7 comments
RFC: Resolver for inclusion of related models
In this pull request, I am proposing a solution for resolving inclusion of related models and demonstrating the viability of the proposed solution. S…
+1,717
−212
•
7
comments
- fix: enforce JsonSchemaOptions type when building model schema
- feat(eslint-config): enable "no-return-await" rule
- build: configure Renovate to update Node.js versions in Travis config
- feat(repository-tests): test `replaceById`, verify plain data handling + more
- test(repository): fix setup of relations with custom FK names
- refactor: clean up after CrudConnectorFeatures rename
- Rename CrudConnectorFeatures to CrudFeatures
- refactor: extract helpers resolving relation metadata into own files
- feat: remove openapi-v3-types package
- feat(repository): add static method Entity.getIdProperties()
- chore(repository-tests): fix the clean script to remove tsbuildinfo
- feat(testlab): improve typings for `toJSON()` helper
- [RFC WIP] feat(health): add a component to run health checks
- Spike/new requestbody
- chore: add repository.directory to package.json
- feat(repository): add beginTransaction API
- build: configure Renovate to update Node.js versions in Travis config
- feat(rest): introduce an interceptor-chain based sequence of actions for REST
- feat: add app.service() and extend service booter to load classes with `@bind`
- [SPIKE] feat: simplify request body decorator
- feat(boot): use @config to inject options for booters
- feat(openapi-v3): allow optional spec for `@param.*` shortcut decorators
- feat(context): allow @config.* to specify the target binding key
- docs: update model decorator
- chore: update api-extractor packages
- RFC: Resolver for inclusion of related models
- feat(context): use invocation context for method dependency injection
- Update templates to make use of `getModelSchemaRef`
- feat(rest-explorer): use configuration apis/decorators
- Update API Docs and test to show that "optional" takes precedence over "partial"
- feat(repository-json-schema): add an option to make properties optional
- Make foreign key property required and other relational properties optional
- fix(cli): add support for excluding custom pk from POST requests
- Add Short-term solution for hiddenProperties in model
- feat(cli): store original cli version in .yo.rc.json
- docs: add Q3 roadmap
- docs: change loopback4-example-shopping clone link
- Some pull request reviews not shown.
Created an issue in strongloop/loopback-next that received 2 comments
Support `inq` splitting in `findByForeignKeys`
Under the hood, inclusion resolvers are implemented using inq operator:
Gather PK/FK values from source models.
Query target models using inq and …
•
2
comments
- Spike: robust handling of ObjectID type for MongoDB
- Reject queries with incompatible "filter.fields" and "filter.include"
- Recursive inclusion of related models
- Include related models with a custom scope
- Blog post: announce Inclusion of related models
- Add inclusion resolvers to `lb4 relation` CLI
- Update `todo-list` example to use inclusion resolver
- Implement InclusionResolver for hasOne relation
- Implement InclusionResolver for belongsTo relation
- Implement InclusionResolver for hasMany relation
- Include related models in `DefaultCrudRepository`
- Introduce `InclusionResolver` concept
- Add `findByForeignKeys` helper (initial version)
- Test relations against databases
- Add `keyFrom` to resolved relation metadata
- Verify relation type in `resolve{Relation}Metadata`
- Reject create/update requests when data contains navigational properties
- Run repository tests for Cloudant
- Run repository tests for PostgreSQL
- Execute raw NoSQL queries (e.g. MongoDB)