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

Create a Code Example to Explain the propagate Property #1145

Open
namnguyen20999 opened this issue Oct 3, 2024 · 6 comments
Open

Create a Code Example to Explain the propagate Property #1145

namnguyen20999 opened this issue Oct 3, 2024 · 6 comments
Labels
📄 Documentation Internal or public documentation 📈 Improvement Improvement of a feature. 🟩 Priority: Low Low priority and doesn't need to be rushed 🔒 Staff only Restricted to CC staff members

Comments

@namnguyen20999
Copy link
Member

Description:
We need to provide a clear code example in the documentation to explain the behavior and use cases of the propagate property in Taipy. This example should demonstrate:

  • How the propagate property works.
  • Any common use cases for this property.

The example should be concise, easy to follow, and should align with the existing style and structure of the documentation.

Acceptance Criteria:

  • A complete code example is created and added to the appropriate section of the documentation.
  • The example demonstrates how the propagate property is used and its effect on the execution flow.
  • The explanation should be clear enough for beginners to understand the concept.

Additional Notes:
Please ensure the example is tested and the documentation is updated accordingly.

@namnguyen20999 namnguyen20999 added 📈 Improvement Improvement of a feature. 📄 Documentation Internal or public documentation 🟩 Priority: Low Low priority and doesn't need to be rushed labels Oct 3, 2024
@manya706
Copy link

manya706 commented Oct 4, 2024

hey! can i work on this?

@jrobinAV
Copy link
Member

jrobinAV commented Oct 7, 2024

Hi @manya706,

You are already assigned to the issue Avaiga/taipy#1411. For the hacktoberfest event, only one issue is assigned at a time.

Thank you for your understanding.

@jrobinAV
Copy link
Member

jrobinAV commented Oct 8, 2024

@manya706
Sorry for my previous answer. Actually, yes, you can work on it, and I can assign it to you, but it is not part of the Hacktoberfest event.

Do you still want to be assigned on it?

Thank you.

@manya706
Copy link

manya706 commented Oct 8, 2024

Yess, thanks :)

Copy link

This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.

@github-actions github-actions bot added the 🥶Waiting for contributor Issues or PRs waiting for a long time label Oct 23, 2024
Copy link

github-actions bot commented Nov 7, 2024

This issue has been unassigned automatically because it has been marked as "🥶Waiting for contributor" for more than 14 days with no activity.

@github-actions github-actions bot removed the 🥶Waiting for contributor Issues or PRs waiting for a long time label Nov 7, 2024
@jrobinAV jrobinAV added the 🔒 Staff only Restricted to CC staff members label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📄 Documentation Internal or public documentation 📈 Improvement Improvement of a feature. 🟩 Priority: Low Low priority and doesn't need to be rushed 🔒 Staff only Restricted to CC staff members
Projects
None yet
Development

No branches or pull requests

3 participants