Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix data in generated pom.xml #48

Merged
merged 2 commits into from
Oct 4, 2019
Merged

Fix data in generated pom.xml #48

merged 2 commits into from
Oct 4, 2019

Conversation

vmax
Copy link
Contributor

@vmax vmax commented Oct 4, 2019

What is the goal of this PR?

Fix #26
Specify fields needed for Maven Central deployment

What are the changes implemented in this PR?

Specify project_name, project_description, project_url and scm_url

@haikalpribadi haikalpribadi merged commit 8d141c0 into master Oct 4, 2019
@vmax vmax deleted the fix-pom-xml branch October 4, 2019 15:55
dmitrii-ubskii pushed a commit that referenced this pull request Aug 25, 2023
Remove `Answer.explanations()` shortcut method that always returned empty set and is not documented and inconsistent with other APIs!
dmitrii-ubskii pushed a commit to dmitrii-ubskii/typedb-driver that referenced this pull request Aug 31, 2023
## What is the goal of this PR?

Our fork of `rules-nodejs` is ~600 commits behind the official upstream repo and it's time to switch to upstream rules so it's easier to keep up.

## What are the changes implemented in this PR?

* Migrate `nodejs_jest_test` to `jasmine_node_test`
  * `it()` instead of `test()` in test definitions
  * `expect(obj).toHaveLength(len)` is not available in Jasmine, so we use `expect(obj.length).toBe(len)`. This corresponds to exact [definition](https://jestjs.io/docs/en/expect.html#tohavelengthnumber) of what original function does.
  * `xit()` instead of `test.skip()`
  * `jasmine.DEFAULT_TIMEOUT_INTERVAL` instead of `jest.setTimeout`
  * `await expectAsync(promise).toBeRejected();` instead of `await expect(promise).rejects.toThrowError();` 
* Use `yarn` to install dependencies instead of `npm`:
  * this is a currently-recommended way by `rules-nodejs` (see their `README`)
  * `grpc` failed to install with `npm_install` — planning to open an issue soon
* Add `node_modules` to `.gitignore` — `rules-nodejs` now install Node deps right into workspace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The pom.xml generated by 'bazel build //:assemble-maven' contains missing info
2 participants