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

Chore/merge new feature #203

Merged
merged 40 commits into from
Jan 16, 2023
Merged

Chore/merge new feature #203

merged 40 commits into from
Jan 16, 2023

Conversation

laboonly
Copy link
Contributor

Submit a pull request for this project.

Why?

What?

How?

mr-kelly and others added 30 commits January 5, 2023 23:26
First release of APITable
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
…er i18n, new env config (#148)

Co-authored-by: wuyitao <wuyitao@vikadata.com>
Co-authored-by: Aria <jianweisummer@gmail.com>
Co-authored-by: 王开朗 <wangkailang@users.noreply.github.com>
Co-authored-by: wangkailang <wangkailang@vikadata.com>
Co-authored-by: paylm <172749114@qq.com>
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->
use multiple feature modules instead of database module
https://github.com/vikadata/vikadata/issues/2659

# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->
split Database module into multiple submodules.

```mermaid
graph TD;
         Database-->Application;
        Actuator-->Application;
        Automation-->Application;
        Fusion-->Application;
        Grpc-->Application;
        User-->Application;;
        Unit-->Application;;
        Developer-->Application;;
        Shared-->Database;
        Shared-->Actuator;
        Shared-->Automation;
        Shared-->Fusion;
        Shared-->Grpc;
        Shared-->User;
        Shared-->Unit;
        Shared-->Developer;
        Attachment-->Database;
        Dashboard-->Database;
        Datasheet-->Database;
        Form-->Database;
        Mirror-->Database;
        Resource-->Database;
        Shared-->Attachment;
        Shared-->Dashboard;
        Shared-->Datasheet;
        Shared-->Form;
        Shared-->Mirror;
        Shared-->Resource;
```

# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
- [x] split Database module into multiple submodules, such as attachment
module, dashboard module, datasheet module, etc.
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?

Add Clinic.js to room-server for performance profiling during local
development. For example, `make run-perf -> 1` will run room-server with
Clinic.js with flamegraph, when room-server is terminated with Ctrl+C,
Clinic.js will generate a flamegraph like below.


![image](https://user-images.githubusercontent.com/5410312/211004013-f5dc17bc-66e1-4690-af23-85eb034de23b.png)


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
# Why? 
sometimes init-db run fail because db changelog lock of liquibase


# What?
cause init-db run waiting timeout


# How?
add pre-action `releaseLocks` in init-db avoid stuck
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
Resolve crashes caused by sanbox widget.
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
replace default billing field parameter
- docs issue template
- question issue template
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
Submit a pull request for this project.

# Why? 
Clear a little bad smell code

# What?
In this component context, while the value equals null, it should be
empty string, so that code at this line needn't repeat union operation

# How?
set empty directly

Co-authored-by: Kelly Chan <kelly@apitable.com>
Co-authored-by: 王开朗 <wangkailang@users.noreply.github.com>
# Why? 
Improve the design and layout of the email verify HTML to make it more
visually appealing and user-friendly. The current design is too basic
and only contains the text.

# What?
Make it more interactive and engaging, with appropriate use of images
and other multimedia elements if relevant. Additionally, consider adding
helpful prompts and instructions to guide users through the verification
process.

# How?
Add an image and replace the old text.
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->
user can't send email by gmail and outlook
# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->
user can send email by gmail and outlook

# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
modify mail port and ssl config
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->
register user default avatar may be null

# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->
register user default avatar not be null

# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
modify default avatar color random number
mr-kelly and others added 10 commits January 13, 2023 22:08
Bumps [class-validator](https://github.com/typestack/class-validator)
from 0.12.2 to 0.14.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/typestack/class-validator/blob/develop/CHANGELOG.md">class-validator's
changelog</a>.</em></p>
<blockquote>
<h3><a
href="https://github.com/typestack/class-validator/compare/v0.13.2...v0.14.0">0.14.0</a>
(2022-12-09)</h3>
<h3>Added</h3>
<ul>
<li>add <code>@IsTimeZone</code> decorator to check if given string is
valid IANA time zone</li>
<li>add <code>@IsISO4217CurrencyCode</code> decorator to check if the
string is an ISO 4217 currency code</li>
<li>add <code>@IsStrongPassword</code> decorator to check if given
password matches specific complexity criteria</li>
<li>add <code>@IsBase58</code> decorator to check if a string is base58
encoded</li>
<li>add <code>@IsTaxId</code> decorator to check if a given string is a
valid tax ID in a given locale</li>
<li>add support for passing function as date generator in
<code>@MinDate</code> and <code>@MaxDate</code> decorators</li>
<li>add option to print constraint error message instead of constraint
type in validation error</li>
<li>improve decorator metadata lookup performance</li>
<li>return possible values in error message for <code>@IsEnum</code>
decorator</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>re-added <code>@types/validator</code> as dependency</li>
<li>fix error generation when using <code>@NestedValidation</code></li>
<li>pass validation options correctly to validator in
<code>@IsDateString</code> decorator</li>
<li>support passing <code>Symbol</code> as parameter in error message
generation</li>
<li>specify supported locales for <code>@IsAlphanumeric</code>
decorator</li>
<li>correctly assign decorator name in metadata instead of loosing
it</li>
<li>fix various spelling errors in documentation</li>
<li>fix various spelling errors and inconsistencies in JSDoc for
decorators</li>
</ul>
<h3>Changed</h3>
<ul>
<li>enable <code>forbidUnknownValues</code> option by default</li>
<li>remove documentation about deprecated schema based validation and
added warning</li>
<li>update warning message logged about missing decorator metadata</li>
<li>update <code>libphonenumber-js</code> to <code>^1.10.14</code> from
<code>^1.9.43</code></li>
<li>update various dev-dependencies</li>
</ul>
<h3>BREAKING CHANGES</h3>
<p><strong><code>forbidUnknownValues</code> option is enabled by
default</strong></p>
<p>From this release the <code>forbidUnknownValues</code> is enabled by
default. This is the desired behavior for majority of
use-cases, but this change may break validation for some. The two
scenarios that results in failed validation:</p>
<ul>
<li>when attempting to validate a class instance without metadata for
it</li>
<li>when using group validation and the specified validation group
results in zero validation applied</li>
</ul>
<p>The old behavior can be restored via specifying
<code>forbidUnknownValues: false</code> option when calling the validate
functions.</p>
<p>For more details see [PR <a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1798">#1798</a>](<a
href="https://github-redirect.dependabot.com/typestack/class-validator/pull/1798">typestack/class-validator#1798</a>)
and <a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1422#issuecomment-1317953863">#1422
(comment)</a>.</p>
<p><strong><code>@NestedValidation</code> decorator correctly assigns
validation errors</strong></p>
<p>Until now the errors from a nested validation in some cases were
incorrectly assigned</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/typestack/class-validator/commit/5f0d424c164672ec981e24d6e634354803abf25f"><code>5f0d424</code></a>
merge: release 0.14.0 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1841">#1841</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/e3d070836556b73d8396c34a360c4744c9d8363c"><code>e3d0708</code></a>
build: bump version to 0.14.0</li>
<li><a
href="https://github.com/typestack/class-validator/commit/ad7689055d0b92da9d6f4787cd91ec4d5392a9f1"><code>ad76890</code></a>
docs: add changelog for 0.14.0</li>
<li><a
href="https://github.com/typestack/class-validator/commit/9a775c59247f00f2ad911686d335fd8e1f9864be"><code>9a775c5</code></a>
build(deps-dev): bump <code>@​types/node</code> from 18.11.11 to
18.11.12 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1840">#1840</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/53bc9f6fcefea77f17cb8e900178f25ec18b6cbc"><code>53bc9f6</code></a>
build(deps-dev): bump <code>@​typescript-eslint/eslint-plugin</code> (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1837">#1837</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/d9b40721b8911be84ae0a9e40962c6244149c7f4"><code>d9b4072</code></a>
build(deps-dev): bump <code>@​typescript-eslint/parser</code> from
5.45.1 to 5.46.0 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1838">#1838</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/f993e9e44eb6a8cedc8ac076cee9b71760d1829d"><code>f993e9e</code></a>
build(deps-dev): bump typescript from 4.9.3 to 4.9.4 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1835">#1835</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/ad1a41d39dee051c3a43bbd357ee0c1553b54055"><code>ad1a41d</code></a>
build(deps-dev): bump <code>@​rollup/plugin-commonjs</code> from 23.0.3
to 23.0.4 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1836">#1836</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/42b4f7f5a34c118db14c03b6466afb5427678718"><code>42b4f7f</code></a>
build(deps-dev): bump prettier from 2.8.0 to 2.8.1 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1834">#1834</a>)</li>
<li><a
href="https://github.com/typestack/class-validator/commit/0c986d4e74c498876c728c58e1b30169dccec496"><code>0c986d4</code></a>
build(deps-dev): bump <code>@​types/node</code> from 18.11.10 to
18.11.11 (<a
href="https://github-redirect.dependabot.com/typestack/class-validator/issues/1833">#1833</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/typestack/class-validator/compare/v0.12.2...v0.14.0">compare
view</a></li>
</ul>
</details>
<details>
<summary>Maintainer changes</summary>
<p>This version was pushed to npm by <a
href="https://www.npmjs.com/~typestack-release-bot">typestack-release-bot</a>,
a new releaser for class-validator since your current version.</p>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=class-validator&package-manager=npm_and_yarn&previous-version=0.12.2&new-version=0.14.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the
default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as
the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as
the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the
default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/apitable/apitable/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [json5](https://github.com/json5/json5) from 1.0.1 to 1.0.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/json5/json5/releases">json5's
releases</a>.</em></p>
<blockquote>
<h2>v1.0.2</h2>
<ul>
<li>Fix: Properties with the name <code>__proto__</code> are added to
objects and arrays. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/199">#199</a>)
This also fixes a prototype pollution vulnerability reported by Jonathan
Gregson! (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/295">#295</a>).
This has been backported to v1. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/298">#298</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/json5/json5/blob/main/CHANGELOG.md">json5's
changelog</a>.</em></p>
<blockquote>
<h3>Unreleased [<a
href="https://github.com/json5/json5/tree/main">code</a>, <a
href="https://github.com/json5/json5/compare/v2.2.3...HEAD">diff</a>]</h3>
<h3>v2.2.3 [<a
href="https://github.com/json5/json5/tree/v2.2.3">code</a>, <a
href="https://github.com/json5/json5/compare/v2.2.2...v2.2.3">diff</a>]</h3>
<ul>
<li>Fix: json5@2.2.3 is now the 'latest' release according to npm
instead of
v1.0.2. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/299">#299</a>)</li>
</ul>
<h3>v2.2.2 [<a
href="https://github.com/json5/json5/tree/v2.2.2">code</a>, <a
href="https://github.com/json5/json5/compare/v2.2.1...v2.2.2">diff</a>]</h3>
<ul>
<li>Fix: Properties with the name <code>__proto__</code> are added to
objects and arrays.
(<a
href="https://github-redirect.dependabot.com/json5/json5/issues/199">#199</a>)
This also fixes a prototype pollution vulnerability reported by
Jonathan Gregson! (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/295">#295</a>).</li>
</ul>
<h3>v2.2.1 [<a
href="https://github.com/json5/json5/tree/v2.2.1">code</a>, <a
href="https://github.com/json5/json5/compare/v2.2.0...v2.2.1">diff</a>]</h3>
<ul>
<li>Fix: Removed dependence on minimist to patch CVE-2021-44906. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/266">#266</a>)</li>
</ul>
<h3>v2.2.0 [<a
href="https://github.com/json5/json5/tree/v2.2.0">code</a>, <a
href="https://github.com/json5/json5/compare/v2.1.3...v2.2.0">diff</a>]</h3>
<ul>
<li>New: Accurate and documented TypeScript declarations are now
included. There
is no need to install <code>@types/json5</code>. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/236">#236</a>,
<a
href="https://github-redirect.dependabot.com/json5/json5/issues/244">#244</a>)</li>
</ul>
<h3>v2.1.3 [<a
href="https://github.com/json5/json5/tree/v2.1.3">code</a>, <a
href="https://github.com/json5/json5/compare/v2.1.2...v2.1.3">diff</a>]</h3>
<ul>
<li>Fix: An out of memory bug when parsing numbers has been fixed. (<a
href="https://github-redirect.dependabot.com/json5/json5/issues/228">#228</a>,
<a
href="https://github-redirect.dependabot.com/json5/json5/issues/229">#229</a>)</li>
</ul>
<h3>v2.1.2 [<a
href="https://github.com/json5/json5/tree/v2.1.2">code</a>, <a
href="https://github.com/json5/json5/compare/v2.1.1...v2.1.2">diff</a>]</h3>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/json5/json5/commit/a62db1e51e1031d92ac260f5bb38bbed1fdbc754"><code>a62db1e</code></a>
1.0.2</li>
<li><a
href="https://github.com/json5/json5/commit/e0c23fe458a77c0b2cdb271376be5d8d0908133c"><code>e0c23fe</code></a>
docs: update CHANGELOG for v1.0.2</li>
<li><a
href="https://github.com/json5/json5/commit/62a65408408d40aeea14c7869ed327acead12972"><code>62a6540</code></a>
fix: add <strong>proto</strong> to objects and arrays</li>
<li>See full diff in <a
href="https://github.com/json5/json5/compare/v1.0.1...v1.0.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=json5&package-manager=npm_and_yarn&previous-version=1.0.1&new-version=1.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the
default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as
the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as
the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the
default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/apitable/apitable/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Shawn Deng <dengguiheng@apitable.com>
Co-authored-by: Kelly Chan <kelly@apitable.com>
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->
#2832

# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->
add unit test for developer module
- use mock data instead of connecting to a live database
- test all branches in a service with multiple individual tests(it)

# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
- [x] use mock data instead of connecting to a live database
- [x] test all branches in a service with multiple individual tests(it)

Co-authored-by: plodsoft <xplzjwz@gmail.com>
# Why? 
customize server time zone


# What?
timezone is friendly for user who need to deploy difference region


# How?
add time zone environment variables
@laboonly laboonly requested a review from zoe-icu January 16, 2023 14:16
@CLAassistant
Copy link

CLAassistant commented Jan 16, 2023

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
13 out of 14 committers have signed the CLA.

✅ mr-kelly
✅ arucil
✅ alolonghun
✅ networkhermit
✅ wangkailang
✅ JaneSu
✅ wuyitaoBoomboommm
✅ yort-feng
✅ MrWangQAQ
✅ LiuZijingBron
✅ xukecheng
✅ laboonly
✅ shawndenggh
❌ zhou-yg
You have signed the CLA already but the status is still pending? Let us recheck it.

@laboonly laboonly changed the title Chore/merge vikadata Chore/merge new feature Jan 16, 2023
@laboonly laboonly merged commit fe2edbe into release/0.17.0 Jan 16, 2023
@laboonly laboonly deleted the chore/merge-vikadata branch January 16, 2023 14:54
arucil pushed a commit that referenced this pull request Feb 3, 2023
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
wumanho pushed a commit to wumanho/apitable that referenced this pull request Feb 6, 2023
Submit a pull request for this project.

<!-- If you have an Issue that related to this Pull Request, you can
copy this Issue's description -->

# Why? 
<!-- 
> Related to which issue?
> Why we need this pull request?
> What is the user story for this pull request? 
-->


# What?
<!-- 
> Can you describe this feature in detail?
> Who can benefit from it? 
-->


# How?
<!-- 
> Do you have a simple description of how this pull request is
implemented?
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet