Skip to content

Commit 1d5c2e0

Browse files
committed
chore: code sharing
1 parent d2d8129 commit 1d5c2e0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

code-sharing/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ title: Code Sharing
88

99
2. A good code sharing approach should fit naturally in with well supported community standards and not require any extra build tooling just for the sharability to support itself. It should, in other words, stand firmly on it's own in scope of the language it is written in.
1010

11-
3. A good code sharing approach should not have to introduce new file extensions purely for sake of sharability (outside of those naturally supported by the framework) to deal with and otherwise alter the way you think about your code in general. All team's organize code by folders naturally and the same should be matched with good code sharing approaches avoiding new file extensions and concepts that go beyond general code organization.
11+
3. A good code sharing approach should not have to introduce new file extensions purely for sake of sharability (outside of those naturally supported by the framework) to deal with. All team's organize code by folders naturally and the same should be matched with good code sharing approaches avoiding new file extensions and concepts that go beyond general code organization.
1212

1313
4. A good code sharing approach should clearly identify deployment/distribution lines as well as distinct platform separation allowing various shared code segments to have clear designated deployment targets allowing teams to control their own sophisticated build pipelines as they desire. Further the shared code should live within a thoughtful organizational structure that supports the ability to scale and adapt to future needs aside from the deployment targets that use the shared code.
1414

@@ -34,8 +34,8 @@ If a "code sharing solution" is maintained by a framework that can often mean th
3434

3535
**Cons:**
3636

37-
- Some learning curve if not used to Nx practices in general
38-
- Some learning curve if you have not developed applications in large codebases before
37+
- Learning curve if not used to Nx practices in general
38+
- Learning curve if you have not developed applications in large codebases before
3939
- Understanding the [basic fundamentals](https://nstudio.io/xplat/fundamentals/architecture) of the provided architecture
4040

4141
- [Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/)

0 commit comments

Comments
 (0)