-
Notifications
You must be signed in to change notification settings - Fork 172
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
Change the demo of each API to one #455
Comments
Good point! We should do some refactor. We can split this issue into different tasks:
chinese:
|
I will take Delete redundant demos and keep only one demo,which can be used for all File API components |
Is this command only available on mac? I run it on windows and it generates a file that is all messed up |
@GimmeCyy which command are you talking about? Do you me |
@GimmeCyy It's a demo client of Layotto,and to run it successfully, you should start layotto first. |
/good-first-issue cancel |
This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue or help wanted) or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue or help wanted. Thank you for your contributions. |
Now there are multiple demos of each API. For example, there are 5 implementations under the demo of sequencer. This does not prove that layotto is portable. It will be better if a demo can invoke multiple components.
The text was updated successfully, but these errors were encountered: