Docs: Add Custom Code Guide by dericksozo · Pull Request #520 · amplication/docs

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

dericksozo · 2024-09-10T07:03:52Z

(docs): Adding a new guide around adding custom code / business logic to your service after building it. It clarifies the process of merging branches, modifying files, and more.

This PR takes care of #517 and #518.

… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

…rvice guide.

…tom code to your service page.

…g the link on the new guide.

PazYanoverr · 2024-09-19T06:55:48Z

-3. Amplication uses a folder structure that separates customizable and non-customizable code.
-4. The `base` folder contains files that should not be modified, as they will be overwritten by Amplication.
-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.


Maybe instead of saying this- we can say that custom code can be added to all files or such.

PazYanoverr · 2024-09-19T09:15:16Z

-5. Files outside the `base` folder can be safely customized and will be preserved across builds.
+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.


Amplication can update the files in the base folder in each build, but also may update generated code in other files

PazYanoverr · 2024-09-19T09:25:26Z

+1. All code in your Amplication project can be customized.
+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.


They may not be "preserved" as the generated code can be updated there. So I would say something like-
Files outside the base folder are intended for your custom code.

PazYanoverr · 2024-09-19T09:27:09Z

+2. Amplication uses a specific folder structure to manage custom and generated code.
+3. The `base` folder contains generated files that Amplication updates with each build.
+4. Files outside the `base` folder are intended for your custom code and are preserved across builds.
+5. Amplication uses [smart merging](/smart-git-sync) to update your project while preserving your custom code.


I think we should be more clear here and avoid using the word merging (as we merge nothing but suggest a PR that it can be merged).
We should say that Amplication will always respect the custom code that was created by the user and never overwrite it

PazYanoverr · 2024-09-19T09:29:22Z

- ```bash
- git push origin main
- ```
+1. Base files in the `base` folder are regenerated with each build.


The user will get updates in the base file only in case there are relevant changes.
Not sure it's important to mention that the base files (and actually all the generated code) is regenerated every time

PazYanoverr · 2024-09-19T09:55:26Z


-Amplication is designed to preserve your custom code while allowing for continuous updates to the generated code. Here's how it works:
+1. Regenerates base files with each build.
+2. Preserves non-base files containing your custom code.


Again- all custom code is preserved...

PazYanoverr · 2024-09-19T09:58:42Z

+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:

-This approach allows you to freely add custom business logic, new endpoints, or any other customizations while still benefiting from Amplication's code generation and updates.
+1. Amplication will provide clear indications of the conflicting areas.


Using the known git mechanism

PazYanoverr · 2024-09-19T10:00:00Z

+## Handling Conflicts

-4. **Conflict Resolution**: If conflicts arise, Amplication provides clear indications and allows you to resolve them manually.
+While Amplication strives to preserve your custom code, conflicts may arise, especially with significant changes to your data model or entity structure. If conflicts occur:


Let's emphasize that the conflict resolution should take place on 'amplication' branch, and then- merge the result to the main branch

PazYanoverr · 2024-09-19T10:01:06Z

- While Amplication strives to maintain compatibility, major changes to your data model or entity structure may require manual updates to your custom code.
+- While all code can be customized, we recommend focusing custom code in the non-base files for easier maintenance.
+- Major changes to your data model or entity structure may require manual updates to your custom code.
+- Client-side customization (Admin UI) is supported, but changes may not be automatically merged in future builds. Consider maintaining a separate repository for extensive client-side customizations.


Let's remove it. I don't think it adds value here

PazYanoverr · 2024-09-19T10:05:36Z

 ---

-# Add custom code to your services
+# Understanding Custom Code in Amplication


Adding to this comment-
Not sure I understand why we have two separate pages for the custom code. It seems like there is redundancy between the files and the content repeats itself.
I can understand the need to have one page to explain the concepts of the generated code, and custom code, and the other to show an example of updating custom code or such but then- we need to make sure each page has its own "uniqueness" and contribute different things to the subject.
WDYT?

…n/docs into docs/git-sync-updates

…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo · 2024-09-23T10:12:56Z

Hey @PazYanoverr, I implemented your latest feedback. Also, the additional feedback you gave me on the call really helped. I implemented that too. The pages have their own uniqueness, with one focusing on implementation and the other on explanation, as suggested.

My one recommendation is adding a Conclusion section to the end of the implementation guide. Now that the user has this custom code full name retrieval method, what can they do with that? Can they use it in the app, or somewhere else in their code? What are the repercussions? Can we link them to a GitHub repo for a more sophisticated example?

yuval-hazaz · 2024-12-04T08:26:01Z

@dericksozo this one looks good to me - please resolve the conflict and I will approve and merge it

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

(docs): Adding a new guide around adding custom code / business logic…
63d3290
… to your service after building it. It clarifies the process of merging branches, modifying files, and more.

dericksozo added the documentation Improvements or additions to documentation label Sep 10, 2024

dericksozo requested a review from PazYanoverr September 10, 2024 07:03

dericksozo self-assigned this Sep 10, 2024

dericksozo mentioned this pull request Sep 10, 2024
Handling custom code and infrastructure changes using Amplication #517
Open

dericksozo added 3 commits September 10, 2024 17:35

(docs): Updating the previous Custom Code page into a newer and more …
f766d8b
…clear Understanding Code Code page that explains the philosophy and goes into the modifications that might happen to non-base files.

(docs): Adding more examples to the how to add custom code to your se…
10acf27
…rvice guide.

(docs): Fixing the build errors and changing the slug for the add cus…
bcf267b
…tom code to your service page.

dericksozo mentioned this pull request Sep 10, 2024
Update the documentation to reflect possible code changes in the generated customizable (non-base) files #518
Open

(docs): Making sure the broken link is fixed.
331302d

PazYanoverr reviewed Sep 16, 2024
View reviewed changes

dericksozo added 3 commits September 18, 2024 17:20

Merge branch 'main' into docs/git-sync-updates
a4dfac8

(docs): Implementing Paz's feedback.
e636719

(docs): Fixing the error.
6d936b8

dericksozo requested a review from PazYanoverr September 18, 2024 11:52

(docs): Re-writing the original understanding custom code page. Fixin…
8fd6f3e
…g the link on the new guide.

PazYanoverr reviewed Sep 19, 2024
View reviewed changes

dericksozo added 4 commits September 19, 2024 17:31

Merge branch 'main' into docs/git-sync-updates
60dc5ab

(docs): Implementing all of Paz's latest feedback.
196dbc6

Merge branch 'docs/git-sync-updates' ofhttps://github.com/amplicatio…
face2c4
…n/docs into docs/git-sync-updates

(docs): After the call, I have a much better understanding of this. I…
25516bd
…mplementing Paz's feedback, making these pages much easier to read, and flow better.

dericksozo requested a review from PazYanoverr September 23, 2024 10:13

Merge branch 'main' into docs/git-sync-updates
2cbeaf2

dericksozo added 3 commits December 4, 2024 16:15

Merge branch 'main' into docs/git-sync-updates
a4bc821

(docs): Adding a redirect for the new custom code page.
14d9ca6

(docs): Fixing the syntax error.
c86dfa5

Uh oh!

Conversation

dericksozo commented Sep 10, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

dericksozo commented Sep 23, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

yuval-hazaz commented Dec 4, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

dericksozo commented Sep 10, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

dericksozo commented Sep 10, 2024•
edited
Loading

dericksozo commented Sep 23, 2024•
edited
Loading

dericksozo commented Sep 10, 2024•
edited
Loading

dericksozo commented Sep 23, 2024•
edited
Loading

dericksozo commented Sep 10, 2024•
edited
Loading