[
https://issues.apache.org/jira/browse/BEAM-7923?focusedWorklogId=441952&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-441952
]
ASF GitHub Bot logged work on BEAM-7923:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jun/20 18:00
Start Date: 05/Jun/20 18:00
Worklog Time Spent: 10m
Work Description: KevinGG commented on pull request #11884:
URL: https://github.com/apache/beam/pull/11884#issuecomment-639670746
> There's a lot of files there that don't seem relevant; I think we should
go through and figure out what's needed for the actual plugin vs. what's
"extras" that just got copied from a template. We also need to figure out the
distribution story. Will this be released with beam? As another pypi pacakge
(and npm package)?
I can go through these files and explain their usages and the distribution
story. If this is not enough, we can talk offline.
[ESLint](https://eslint.org/docs/user-guide/getting-started)
```
.eslintignore
.eslintrc.js
```
[Github
workflow](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow)
```
# This is later used in the README to display a status badge.
.github/workflows/build.yml
```
[Prettier](https://prettier.io/docs/en/install.html)
```
.prettierignore
.prettierrc.json
```
[Python Packaging](https://packaging.python.org/guides/using-manifest-in/)
```
MANIFEST.in
```
JupyterLab server extension
```
interactive_beam_side_panel/*.py
```
JupyterLab frontend extension
```
src/*.ts[x]
```
JupyterLab frontend extension styles
```
style/*.css
```
JupyterLab configuration
```
jupyter-config/*.json
```
[TypeScript
configuration](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)
```
tsconfig.json
```
[PEP 518](https://www.python.org/dev/peps/pep-0518/)
```
pyproject.toml
```
[npm
package](https://nodejs.org/en/knowledge/getting-started/npm/what-is-the-file-package-json/)
```
package.json
```
The distribution story is
[here](https://jupyterlab.readthedocs.io/en/stable/developer/extension_dev.html#shipping-packages).
The plan is to ship the server extension (PYPI) and the frontend extension
(NPM) separately.
Temporarily, the server extension will just be a placeholder. We only need
to release it once.
The frontend extension can be shipped regularly: `The general idea is to
pack the Jupyterlab extension using npm pack, and then use the data_files logic
in setup.py to ensure the file ends up in the
<jupyterlab_application>/share/jupyter/lab/extensions directory.`
It doesn't have to be released with Beam releases.
If this `sdks/python/apache_beam/runners/interactive` is not a suitable
place to put the code base, we can move it to some other directory in this repo
outside of `sdks`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 441952)
Time Spent: 23h 50m (was: 23h 40m)
> Interactive Beam
> ----------------
>
> Key: BEAM-7923
> URL: https://issues.apache.org/jira/browse/BEAM-7923
> Project: Beam
> Issue Type: New Feature
> Components: runner-py-interactive
> Reporter: Ning Kang
> Assignee: Ning Kang
> Priority: P2
> Labels: stale-assigned
> Time Spent: 23h 50m
> Remaining Estimate: 0h
>
> This is the top level ticket for all efforts leveraging [interactive
> Beam|[https://github.com/apache/beam/tree/master/sdks/python/apache_beam/runners/interactive]]
> As the development goes, blocking tickets will be added to this one.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
